-
Type: Bug
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Index Maintenance, Querying
-
None
-
ALL
Our documentation on multikey behavior and bounds creation is incomplete. Also our bounds w/the new planner are probably not as tight as they could be.
- is related to
-
SERVER-7959 Potentially unexpected scans with compound indexes when some fields are multikey
- Closed
-
SERVER-12281 When choosing multikey index bounds, never choose a superset if a subset is available
- Backlog
- related to
-
SERVER-12475 Query on compound multi-key indexes lost performance between 2.4.6 and 2.5.5-pre-
- Closed