[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()
{
"version" : "2.1.0",
"gitVersion" : "d674c681170337e3dfc34ae796b06fdde5ac05dd",
"sysInfo" : "Linux ip-10-110-9-236 2.6.21.7-2.ec2.v1.2.fc8xen #1 SMP Fri Nov 20 17:48:28 EST 2009 x86_64 BOOST_LIB_VERSION=1_41",
"versionArray" : [
2,
1,
0,
0
],
"bits" : 64,
"debug" : false,
"maxBsonObjectSize" : 16777216,
"ok" : 1
}


Issue Links:
Related
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'}

)
point not in interval of [ -180, 180 )

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>
Date: Mon Jul 2 15:39:39 2012 -0700
"added feedback when points are out of bounds"
Branch: master
https://github.com/mongodb/mongo/commit/f843e4f1cad1dd9ac808f91c3ff323fdd9886860

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.
Putting in the _id is definitely important.

Generated at Thu Feb 08 03:09:29 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.