-
Type: Bug
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Querying
-
Fully Compatible
-
ALL
Currently we just output a collscan if we see a NOT/NOR. This is too conservative. We should just not descend down a not/nor when tagging the pred tree and go through planning as usual. Enumeration should stop if it sees a negation as well. This way we'll still affix a negation as a filter if there's an and-related pred that can use an index.
- is depended on by
-
SERVER-10005 $exists:false prevents use of a sparse index on a different field
- Closed
-
SERVER-10608 {$exists: false} will not use index
- Closed
-
SERVER-11821 Indexes are ignored with use of $not in 2.5, obeyed in 2.4
- Closed
-
SERVER-11839 index is not used to provide sort for $not query
- Closed