[SERVER-7566] simpler way to figure out if an index is multikey Created: 06/Nov/12  Updated: 31/Jan/24

Status: Backlog
Project: Core Server
Component/s: Index Maintenance
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Ross Lawley Assignee: Backlog - Query Execution
Resolution: Unresolved Votes: 15
Labels: storch
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Duplicate
is duplicated by SERVER-36183 collection.getIndexes() should displa... Closed
Related
related to SERVER-15086 Allow for efficient range queries ove... Closed
Assigned Teams:
Query Execution
Participants:
Case:

 Description   

Determining if an index is multikeyed isn't simple - you have to write a query that uses the index and run explain(). It would be useful if you could discover it by just doing db.things.getIndexes()



 Comments   
Comment by Asya Kamsky [ 20/Aug/18 ]

Reassessing in next triage meeting.

Determine if it's feasible to add multikey data to $indexStats

Comment by Adam Harrison [ 01/Aug/18 ]

Could this ticket be reassessed in terms of priority?

I created SERVER-36183 which was just recently merged into this ticket. As I described in that ticket, recent changes in MongoDB 3.2, 3.4 and 3.6 have introduced behaviors that are dependent on the version and multikeyness of an index. This is a significant behavior change from MongoDB 2.2 / 2.4 when this ticket was created and prioritized.

Comment by Eliot Horowitz (Inactive) [ 06/Nov/12 ]

getIndexes should only return schema information, not stats.
Could put this in db.foo.stats() maybe

Generated at Thu Feb 08 03:14:54 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.