[SERVER-4531] new process for selecting a geo index when performing exact lookup queries Created: 20/Dec/11  Updated: 11/Jul/16  Resolved: 21/Dec/11

Status: Closed
Project: Core Server
Component/s: Geo, Querying
Affects Version/s: None
Fix Version/s: 2.1.0

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

Issue Links:
Related
related to SERVER-8768 implement support for interleaving bt... Closed
Participants:

 Description   

Has been decided that we should implement the following policy for selecting geo cursors when performing an exact lookup:

  • If a geo cursor is a candidate and no btree cursors are candidates, use the geo cursor only.
  • Otherwise don't use a geo cursor.


 Comments   
Comment by auto [ 20/Dec/11 ]

Author:

{u'login': u'astaple', u'name': u'Aaron', u'email': u'aaron@10gen.com'}

Message: SERVER-4531 select only geo index for direct lookup when no btree index is suitable
Branch: master
https://github.com/mongodb/mongo/commit/cc37fe348d61291f2e9a1d8e12334184020c9f9b

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