[SERVER-5635] Feedback when 2D index values are out of range Created: 17/Apr/12 Updated: 11/Jul/16 Resolved: 30/Aug/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Geo |
| Affects Version/s: | 2.1.0 |
| Fix Version/s: | 2.3.0 |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Doug Hudson | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
> db.serverBuildInfo() |
||
| Issue Links: |
|
||||
| Participants: | |||||
| Description |
|
If there are invalid values when attempting to add a 2d index, the feeback has a couple of issues. > db.some_collection.ensureIndex( {geo:'2d'}) Trivially, it is mixing a square bracket and parenthesis, but more importantly it would be nice to have some indication as to which record is causing the problem, by showing the offending value and _id (for instance). It isn't hard to issue queries to track this down, but some information could be helpful. |
| Comments |
| Comment by Daniel Pasette (Inactive) [ 26/Nov/12 ] |
|
Author: Akshay Nathan <akshaynathan@Akshays-MacBook-Air.local> |
| Comment by Doug Hudson [ 19/Apr/12 ] |
|
I didn't know about the bracket use, thanks. |
| Comment by Eliot Horowitz (Inactive) [ 18/Apr/12 ] |
|
The mixed bracket is on purpose to differentiate inclusive vs. exclusive. |