[SERVER-4975] covered index projection may be improperly applied after index becomes multikey during yield Created: 15/Feb/12 Updated: 14/May/15 Resolved: 14/May/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: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Operating System: | ALL | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
We currently support projections for non multikey indexes, but not multikey indexes. If an index becomes multikey during a yield, we may return results that are not proper projections of actual documents. For example, if {a:[1,2]} is saved during a yield making the index {a:1} multikey we may return {a:1} and {a:2} even though there may not be any documents that should be projected to {a:1} or {a:2}. This issue affects yielding in both query and get more. A test demonstrating the issue will be pushed. |
| Comments |
| Comment by David Storch [ 28/Jan/15 ] | ||||||||||||||||||
|
Simple repro script:
| ||||||||||||||||||
| Comment by auto [ 15/Feb/12 ] | ||||||||||||||||||
|
Author: {u'login': u'astaple', u'name': u'Aaron', u'email': u'aaron@10gen.com'}Message: |