-
Type:
Bug
-
Resolution: Won't Fix
-
Priority:
Minor - P4
-
None
-
Affects Version/s: None
-
Component/s: Storage
-
None
-
ALL
-
Execution Team 2020-06-29, Execution Team 2020-07-13, Execution Team 2020-09-21, Execution Team 2020-11-16, Execution Team 2020-11-30
On a collection t with two indexes a_1 (ready) and b_1 (in-progress), the listIndexes command with the option includeBuildUUIDs set to true reports slightly different results for the index b_1 across 4.4 (with FCV=4.2) and a 4.2 binary:
4.2 binary:
foo:PRIMARY> db.runCommand({listIndexes: 't', includeBuildUUIDs: true})
{
"cursor" : {
"id" : NumberLong(0),
"ns" : "test.t",
"firstBatch" : [
{
"v" : 2,
"key" : {
"_id" : 1
},
"name" : "_id_",
"ns" : "test.t"
},
{
"v" : 2,
"key" : {
"a" : 1
},
"name" : "a_1",
"ns" : "test.t"
},
{
"spec" : {
"v" : 2,
"key" : {
"b" : 1
},
"name" : "b_1",
"ns" : "test.t"
},
"buildUUID" : UUID("2deadfcd-c9c3-4f18-8875-3a2f30294bf3")
}
]
},
"ok" : 1,
...
}
4.4 binary (with FCV 4.2):
foo:PRIMARY> db.runCommand({listIndexes: 't', includeBuildUUIDs: true})
{
"cursor" : {
"id" : NumberLong(0),
"ns" : "test.t",
"firstBatch" : [
{
"v" : 2,
"key" : {
"_id" : 1
},
"name" : "_id_"
},
{
"v" : 2,
"key" : {
"a" : 1
},
"name" : "a_1"
},
{
"v" : 2,
"key" : {
"b" : 1
},
"name" : "b_1"
}
]
},
"ok" : 1,
...
}
The includeBuildUUIDs option is an experimental option for the listIndexes command in 4.2 and is not currently used in 4.4 (with FCV 4.2).
- is related to
-
-
- Closed
-
-
SERVER-37839 Identify in-progress index builds as building in the index specs that the listIndexes command returns
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-