[SERVER-36183] collection.getIndexes() should display multikey metadata Created: 18/Jul/18 Updated: 06/Dec/22 Resolved: 27/Jul/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying |
| Affects Version/s: | 3.4.0, 3.6.0 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Adam Harrison | Assignee: | Backlog - Query Team (Inactive) |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Query
|
||||||||
| Participants: | |||||||||
| Description |
|
MongoDB 3.6 introduces compatibility changes regarding the ability of a multikey index to be used in sorting (https://jira.mongodb.org/browse/SERVER-15086). To summarize: In MongoDB 3.6:
Given the performance implications, and that the indexes already contain this information, collection.getIndexes() should:
|
| Comments |
| Comment by Ian Whalen (Inactive) [ 27/Jul/18 ] |
|
Thanks for reporting Adam. We're closing as dupe of SERVER-7566 - please feel free to vote and watch that ticket. Note that the best solution to this might not entail changes to getIndexes but we believe that ticket tracks the work to more simply determine the multikey metadata. |
| Comment by Nick Brewer [ 25/Jul/18 ] |
|
adamaharrison@gmail.com Thanks for your suggestion - I'm passing this along to our Query team as a feature request. -Nick |