[SERVER-11446] don't punt all not/nor to collscan. Created: 29/Oct/13 Updated: 11/Jul/16 Resolved: 04/Dec/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying |
| Affects Version/s: | None |
| Fix Version/s: | 2.5.5 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | hari.khalsa@10gen.com | Assignee: | Benety Goh |
| Resolution: | Done | Votes: | 0 |
| Labels: | query_triage | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||||||||||||||||||
| Issue Links: |
|
||||||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||
| Description |
|
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. |
| Comments |
| Comment by Githook User [ 04/Dec/13 ] |
|
Author: {u'username': u'benety', u'name': u'Benety Goh', u'email': u'benety@mongodb.com'}Message: |