[SERVER-8549] Not in covered index query does not have nscannedObjects = 0 Created: 13/Feb/13 Updated: 15/Feb/13 Resolved: 13/Feb/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Sridhar Nanjundeswaran | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
> db.version() |
||
| Issue Links: |
|
||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||
| Steps To Reproduce: |
testDB = db.getSiblingDB("qa293") ) ) ) ) ) ) // Test not in query ).hint( {foo:1}).explain() |
||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Description |
|
Expecting a covered index query to have nscannedObjects to be 0 with a nin query on the indexed field. This is the case when the index is a regular, unique or sparse unique. |
| Comments |
| Comment by Aaron Staple [ 13/Feb/13 ] |
|
Hi Sridhar - in this case nscannedObjects is being reported based on the current matching implementation which does not implement covered index matching for $nin predicates. The ticket for implementing that in this case is |
| Comment by Sridhar Nanjundeswaran [ 13/Feb/13 ] |
|
Error on the assert is assert: [0] != [28] are not equal : simple.1.8 - nscannedObjects should be 0 for covered query |