[SERVER-26921] Parallel array check in key generation is inconsistent with multikey definition Created: 05/Nov/16 Updated: 27/Jan/17 Resolved: 27/Jan/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Naresh Muddakkagari | 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 | ||||||||
| Sprint: | Query 2017-02-13 | ||||||||
| Participants: | |||||||||
| Description |
on winningPlan "isMultiKey" : false. when i insert single element array still the multikey is false
on winningPlan "isMultiKey" : false. in contrast
is not allowed though i is a single element array! |
| Comments |
| Comment by David Storch [ 27/Jan/17 ] | |||||||||||||||||||||||
|
Hi mnareshy, In commit c7c8e4151d under
You can see from the explain that the index {i: 1, j: 1} is considered multikey due to field j being tracked as a multikey path. The only indexed array contains a single-element, so this demonstrates that single-element indexed arrays are now considered multikey. Since the definition of multikey is now consistent with the parallel array check, I'm resolving this ticket as a duplicate of Best, | |||||||||||||||||||||||
| Comment by Kelsey Schubert [ 08/Nov/16 ] | |||||||||||||||||||||||
|
Hi mnareshy, Thank you for the detailed description of this behavior. I've assigned this ticket to the Query Team for further investigation. Please continue to watch for updates. Kind regards, |