-
Type:
Improvement
-
Resolution: Done
-
Priority:
Minor - P4
-
Affects Version/s: 2.1.0
-
Component/s: Geo
-
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
}
> 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 }
-
None
-
None
-
None
-
None
-
None
-
None
-
None
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.