[SERVER-12470] document and audit multikey bounds behavior Created: 24/Jan/14  Updated: 11/Jul/16  Resolved: 12/Feb/14

Status: Closed
Project: Core Server
Component/s: Index Maintenance, Querying
Affects Version/s: None
Fix Version/s: 2.6.0-rc0

Type: Bug Priority: Major - P3
Reporter: hari.khalsa@10gen.com Assignee: David Storch
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-12475 Query on compound multi-key indexes l... Closed
is related to SERVER-7959 Potentially unexpected scans with com... Closed
is related to SERVER-12281 When choosing multikey index bounds, ... Backlog
is related to DOCS-2703 Doc index bounds behavior for multike... Closed
Operating System: ALL
Participants:

 Description   

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.



 Comments   
Comment by Githook User [ 10/Feb/14 ]

Author:

{u'username': u'dstorch', u'name': u'David Storch', u'email': u'david.storch@10gen.com'}

Message: SERVER-12470 SERVER-12475 SERVER-9532 fix multikey index bounds for compound indices and elemMatch

The new query system multikey index bounds behavior now largely matches that of 2.4.
For a detailed description of the rules for building multikey index bounds, see
the long comment atop db/query/planner_access.h.
Branch: master
https://github.com/mongodb/mongo/commit/bbca96a512c580f13e044eeb7de15132fb3ce193

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