[SERVER-18958] Optimize default covering levels of queried regions in geo queries Created: 12/Jun/15  Updated: 05/Feb/16  Resolved: 20/Jul/15

Status: Closed
Project: Core Server
Component/s: Geo
Affects Version/s: None
Fix Version/s: 3.1.6

Type: Improvement Priority: Minor - P4
Reporter: Kevin Albertson Assignee: Kevin Albertson
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-19168 Finer default indexed level for index... Closed
Duplicate
is duplicated by SERVER-18724 findOne with $near force scan whole c... Closed
Related
is related to SERVER-19267 Manual configuration of geo 2dsphere ... Closed
Backwards Compatibility: Fully Compatible
Participants:

 Description   

For geo queries on small and dense datasets with small limits, the initial coverings are often too large. This can result in fetching many more documents than necessary to satisfy the query. This is the cause of the issue described in SERVER-18724.

To remedy this, we should increase the finest possible query region covering. This includes both the annuluses used in geo near queries and any region supplied to in an intersects or within query.



 Comments   
Comment by Githook User [ 17/Jul/15 ]

Author:

{u'username': u'kevinAlbs', u'name': u'Kevin Albertson', u'email': u'kevin.albertson@10gen.com'}

Message: SERVER-18958 Changes geo query covering levels
Branch: master
https://github.com/mongodb/mongo/commit/d9a9884a6fb07fb29e1787c136c8a360bda6c197

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