[SERVER-3051] Spherical query assertions should provide useful information in case of long/lat order issues. Created: 05/May/11 Updated: 12/Jul/16 Resolved: 06/May/11 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Geo |
| Affects Version/s: | None |
| Fix Version/s: | 1.9.1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Bernie Hackett | Assignee: | Greg Studer |
| Resolution: | Done | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
ALL |
||
| Operating System: | ALL |
| Participants: |
| Description |
|
Users are being tripped up by the caveats related to spherical queries, especially the long/lat order requirement. If you use lat/long order queries will raise an assertion similar to this: error: { "$err" : "assertion db/geo/2d.cpp:1385" }This is so common that the assert should really give a hint as to what the problem is. Here's some example code for repro steps: // Wrong! ); ); ); // Correct > db.points.drop() ); ); ); |
| Comments |
| Comment by Greg Studer [ 06/May/11 ] |
|
related to |