[SERVER-2968] Exact geo lookups not processed exactly Created: 20/Apr/11 Updated: 12/Jul/16 Resolved: 11/May/11 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Geo |
| Affects Version/s: | 1.6.4 |
| Fix Version/s: | 1.9.1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Greg Studer | Assignee: | Greg Studer |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Participants: |
| Description |
|
Exact (single-location) geo lookups only use the hash key, due to the way the query optimizer works. Forcing a document check won't fix this either, since locations may be stored in a variety of formats in the document. |
| Comments |
| Comment by auto [ 11/May/11 ] |
|
Author: {u'login': u'gregstuder', u'name': u'gregs', u'email': u'greg@10gen.com'}Message: use 2d index for exact matches too - |
| Comment by auto [ 09/May/11 ] |
|
Author: {u'login': u'gregstuder', u'name': u'gregs', u'email': u'greg@10gen.com'}Message: Revert "exact checks for 2d queries This reverts commit 174d466dace8c62668bc671740832e14c64a044a. |
| Comment by auto [ 09/May/11 ] |
|
Author: {u'login': u'gregstuder', u'name': u'gregs', u'email': u'greg@10gen.com'}Message: exact checks for 2d queries |
| Comment by Greg Studer [ 21/Apr/11 ] |
|
fix waiting for 1.9.1 |