-
Type: Bug
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Querying
-
None
-
ALL
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.
- duplicates
-
SERVER-18476 In-progress queries may return incorrect results if an index concurrently becomes multikey
- Backlog
- related to
-
SERVER-17678 IndexScan doesn't dedup if index becomes multikey during query execution
- Closed