[DOCS-179] geo docs say you can only have one geo index per collection Created: 02/Apr/12  Updated: 06/Apr/12  Resolved: 06/Apr/12

Status: Closed
Project: Documentation
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Minor - P4
Reporter: Kevin Hanson Assignee: Sam Kleinman (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:
Days since reply: 11 years, 45 weeks, 5 days ago

 Description   

The docs at http://www.mongodb.org/display/DOCS/Geospatial+Indexing say that you can only have one geo index per collection, but I created two in a test collection, and I got no errors.



 Comments   
Comment by Sam Kleinman (Inactive) [ 06/Apr/12 ]

Amended the page to reflect the reasons for this note.

Comment by Greg Studer [ 03/Apr/12 ]

Basically, geoNear will select an undefined index.

Comment by Sam Kleinman (Inactive) [ 02/Apr/12 ]

Is there something more than, "queries can't use more than one index at a time," that creates this limitation for geo indexes or is there something else at play here?

Comment by Greg Studer [ 02/Apr/12 ]

Yep. You can do this, it's just not really supported. We should really throw an error though.

Generally, this comes about when people want to do something like "find near source and destination". We don't support these queries even if multiple indices were present, so it's been seen as low-priority.

Comment by Sam Kleinman (Inactive) [ 02/Apr/12 ]

Greg, Assigning to you just for a fact check. Is this correct? Is something more complicated at work here?

Generated at Thu Feb 08 07:38:06 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.