[SERVER-23112] Update index bounds generation rules for 2dsphere indexes in the PlanEnumerator given path-level multikey info Created: 14/Mar/16  Updated: 26/Apr/16  Resolved: 19/Apr/16

Status: Closed
Project: Core Server
Component/s: Querying
Affects Version/s: None
Fix Version/s: 3.3.5

Type: Improvement Priority: Major - P3
Reporter: Max Hirschhorn Assignee: Max Hirschhorn
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-23906 Enable path-level multikey tracking f... Closed
Related
is related to SERVER-22401 Implement index bounds generation rul... Closed
Backwards Compatibility: Fully Compatible
Sprint: Query 13 (04/22/16)
Participants:

 Comments   
Comment by Githook User [ 19/Apr/16 ]

Author:

{u'username': u'visemet', u'name': u'Max Hirschhorn', u'email': u'max.hirschhorn@mongodb.com'}

Message: SERVER-23112 Assign predicates to 2dsphere indexes using multikey paths.

The metadata in the IndexEntry struct indicates what prefixes of the
indexed fields cause the index to be multikey. This information is used
to get tighter bounds by assigning additional predicates to the index.
Branch: master
https://github.com/mongodb/mongo/commit/d74720487db590a1ff1b39296601806e8d0067d5

Comment by Githook User [ 19/Apr/16 ]

Author:

{u'username': u'visemet', u'name': u'Max Hirschhorn', u'email': u'max.hirschhorn@mongodb.com'}

Message: SERVER-23112 Check baseBounds of $near queries in QueryPlannerTest.

Changes the form of "geoNear2dsphere" query solutions accepted by
QueryPlannerTestLib. The structure now resembles that of "ixscan" query
solutions, where the index key pattern is embedded within a "pattern"
field and index bounds can optionally be specified within a "bounds"
field.
Branch: master
https://github.com/mongodb/mongo/commit/4454864060be01d7e5a1cdb81617822f7bd9e813

Generated at Thu Feb 08 04:02:24 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.