[SERVER-3653] Issues with multiple spatial indexes Created: 19/Aug/11  Updated: 10/Dec/14  Resolved: 27/Feb/14

Status: Closed
Project: Core Server
Component/s: Geo
Affects Version/s: 1.9.2
Fix Version/s: None

Type: Bug Priority: Minor - P4
Reporter: Kyle Banker Assignee: hari.khalsa@10gen.com
Resolution: Duplicate Votes: 5
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-2331 Allow more than one geo index per col... Closed
is duplicated by SERVER-12942 Multiple geoSpatial indexes in a coll... Closed
is duplicated by SERVER-4221 Working with a large set of geospatia... Closed
Related
is related to SERVER-3277 More specific explain() for geo queries Closed
is related to SERVER-9842 Inconsistent and undocumented behavio... Closed
is related to SERVER-11379 require field name in geoNear, remove... Closed
Operating System: ALL
Participants:

 Description   

We currently say in the docs that we allow only one spatial index per collection. However:

  • It's possible to create more than on spatial index on a collection, and $near queries seem to work on them.
  • geoNear commands always fail when there's more than one spatial index.

We should either:

  • Enforce the single spatial index constraint

or

  • Allow the user to specify which field to search using the geoNear command, and remove the limitation from the docs.


 Comments   
Comment by Daniel Pasette (Inactive) [ 27/Feb/14 ]

This will be fixed with SERVER-2331. But not in 2.6.0

Comment by Greg Studer [ 22/Aug/11 ]

need to also address hint()ing with geoSpatial queries when this is done.

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