[SERVER-2115] Geospatial index queries on the X axis do not return the correct results when min/max is set Created: 18/Nov/10  Updated: 12/Jul/16  Resolved: 11/Apr/11

Status: Closed
Project: Core Server
Component/s: Geo
Affects Version/s: 1.6.4, 1.9.1
Fix Version/s: 1.9.0

Type: Bug Priority: Major - P3
Reporter: Jacques Crocker Assignee: Greg Studer
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Mac OS X 1.6.5, MongoDB 1.6.4RC0


Attachments: File bug_repro.rb    
Operating System: ALL
Participants:

 Description   

An error was introduced in 1.6.3 -> 1.6.4 that causes specific queries on the X axis (y = 0) to not return the correct results (only when min,max is set on the query).

Snippet to reproduce the bug is available here: https://gist.github.com/705082



 Comments   
Comment by Greg Studer [ 11/Apr/11 ]

2115

Comment by auto [ 11/Apr/11 ]

Author:

{u'login': u'gregstuder', u'name': u'gregs', u'email': u'greg@10gen.com'}

Message: working exact distance checks for 2d queries SERVER-2115
Branch: master
https://github.com/mongodb/mongo/commit/4e4a1c2b282d071568553f92e9c40f3db7c71ff0

Comment by Greg Studer [ 24/Mar/11 ]

It's an issue with geospatial precision, looking into it. Workaround seems to be to set :bits => 32 (26 by default) in the index for now.

Comment by Jacques Crocker [ 18/Nov/10 ]

Edit... this only fails when min and max are WAY too big

changing it to something smaller:

:min=>-10_000_000, :max=>10_000_000

causes it to work

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