[SERVER-17678] IndexScan doesn't dedup if index becomes multikey during query execution Created: 20/Mar/15 Updated: 06/Nov/17 Resolved: 14/May/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Index Maintenance, Querying |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Mathias Stearn | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | todo_in_code | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Operating System: | ALL | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
IndexScan currently sets _shouldDedup based on the value of isMultiKey at the start of the query. This is incorrect since the index may later become multikey. Note that it isn't enough to recheck isMultiKey after yielding since we would need to know all RecordIds we've already returned. |