[SERVER-1364] don't require scan and order when sort spec can have only one value Created: 06/Jul/10 Updated: 01/Apr/15 Resolved: 01/Apr/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Aaron Staple | Assignee: | David Storch |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Participants: |
| Description |
|
| Comments |
| Comment by Aaron Staple [ 19/Jul/11 ] |
|
I think because of what we did for |
| Comment by Aaron Staple [ 30/Mar/11 ] |
|
We probably don't want to do this right now, because this optimization is only valid when the equality field is not multikey, and if the query yields the equality field could become multikey even if it was not before. And it wouldn't be possible to then switch on scan and order if the multikey status changes. |