-
Type: Bug
-
Resolution: Done
-
Priority: Minor - P4
-
Affects Version/s: None
-
Component/s: Diagnostics, Index Maintenance, Querying
-
Fully Compatible
-
ALL
Expected indexOnly:false but it is reported as true.
skipjack:test> db.foo.find() { "_id" : ObjectId("4fa2ad3315f3f440e6aee399"), "a" : 1, "b" : 2 } { "_id" : ObjectId("4fa2ad3715f3f440e6aee39a"), "a" : 2, "b" : 2, "c" : 2 } skipjack:test> db.foo.find({a: 1, b:2, c: {$exists: false}}, {_id: 0, a:1}).explain().indexOnly true skipjack:test> db.foo.find({a: 1, b:2, c: {$exists: false}}, {_id: 0, a:1, c:1}).explain().indexOnly false skipjack:test> db.foo.getIndexKeys() [ { "_id" : 1 }, { "a" : 1, "b" : 1 } ]
- is duplicated by
-
SERVER-8549 Not in covered index query does not have nscannedObjects = 0
- Closed
-
SERVER-8551 Exists query with a sparse index should have nscannedObjects = 0
- Closed
-
SERVER-8562 indexOnly should be false when sorting by a non indexed field
- Closed
-
SERVER-10959 indexOnly is wrong sometimes
- Closed
- is related to
-
SERVER-4161 nscannedObjects is not calculated properly for covered index queries
- Closed
- related to
-
SERVER-5019 covered indexes are not implemented for scan and order sorts
- Closed
-
SERVER-10448 Revamp explain() formatting
- Closed