[SERVER-13538] Inconsistent geoNear result for MongoDB 2.6.0 and MongoDB 2.4.10 Created: 10/Apr/14 Updated: 10/Dec/14 Resolved: 01/May/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Geo |
| Affects Version/s: | 2.6.0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Titi Wangsa Damhore | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Steps To Reproduce: | run these commands on MongoDB 2.4.10 and 2.6.0
|
||||||||
| Participants: | |||||||||
| Description |
|
geoNear is reporting slightly different result on same dataset depending on the MongoDB version. 420.8260 rounded to 4 decimal points (2.6.0) |
| Comments |
| Comment by Kamran K. [ 01/May/14 ] |
|
Thanks for the bug report. I'm resolving this as a duplicate of Please follow that ticket for further updates on the geoNear issue. |