[SERVER-13618] Optimization for sorted $in queries not applied to reverse sort order Created: 16/Apr/14 Updated: 11/Jul/16 Resolved: 17/Apr/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying |
| Affects Version/s: | 2.6.0 |
| Fix Version/s: | 2.6.1, 2.7.0 |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | David Storch | Assignee: | David Storch |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Operating System: | ALL | ||||||||||||
| Backport Completed: | |||||||||||||
| Participants: | |||||||||||||
| Description |
|
Issue Status as of April 21, 2014 ISSUE SUMMARY USER IMPACT WORKAROUNDS RESOLUTION AFFECTED VERSIONS PATCHES Original descriptionSay we have index {a: 1, b: 1, c: 1} and we issue the following query:
The explode for scans hack (see
We should be able to do the same thing for query
simply by reversing the direction of the index scans. However, explodeForSort() fails and we end up creating a plan with a blocking sort for the query with .sort({c: -1}). |
| Comments |
| Comment by Githook User [ 17/Apr/14 ] |
|
Author: {u'username': u'dstorch', u'name': u'David Storch', u'email': u'david.storch@10gen.com'}Message: |
| Comment by Githook User [ 17/Apr/14 ] |
|
Author: {u'username': u'dstorch', u'name': u'David Storch', u'email': u'david.storch@10gen.com'}Message: |