[SERVER-2386] Geo indexing fails when min/max margins around included locations < 1 Created: 21/Jan/11 Updated: 12/Jul/16 Resolved: 17/Mar/11 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Geo, Index Maintenance |
| Affects Version/s: | 1.7.4 |
| Fix Version/s: | 1.9.0 |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Greg Studer | Assignee: | Greg Studer |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Linux 2.6.35-24-generic #42-Ubuntu SMP Thu Dec 2 02:41:37 UTC 2010 x86_64 GNU/Linux |
||
| Attachments: |
|
| Operating System: | ALL |
| Participants: |
| Description |
|
When the min/max of an ensureIndex( { loc : "2d" }, {min, max}) call are anything less than a single unit greater than or less than any of the locations being indexed, we get the following exception (failed assertation): > t.ensureIndex( { loc : "2d" }, { max : 1 + epsilon, min : -1 - epsilon }) for test.borders The attachment has a testcase which should reproduce the issue (creates a square with points from [-1, 1] on both axes, tries to index with a max of 1.99 and min of -0.99. Same issue tested on smaller squares of points too.) |
| Comments |
| Comment by auto [ 15/Mar/11 ] |
|
Author: {u'login': u'gregstuder', u'name': u'gregs', u'email': u'greg@10gen.com'}Message: double bounds for geo query scaling and addn'l error msgs |
| Comment by Greg Studer [ 21/Jan/11 ] |
|
Forgot to add, could be an issue if indexing sets of locations with very small magnitudes, the margin required around locations is much larger than the location range and may eat up accuracy. |