[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: |
|
||||||||||||||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||||||
| Description |
|
We currently say in the docs that we allow only one spatial index per collection. However:
We should either:
or
|
| Comments |
| Comment by Daniel Pasette (Inactive) [ 27/Feb/14 ] |
|
This will be fixed with |
| Comment by Greg Studer [ 22/Aug/11 ] |
|
need to also address hint()ing with geoSpatial queries when this is done. |