[SERVER-4247] allow non-geo fields to be first indexed field in '2d' index type Created: 10/Nov/11 Updated: 22/Mar/23 |
|
| Status: | Open |
| Project: | Core Server |
| Component/s: | Geo |
| Affects Version/s: | None |
| Fix Version/s: | features we're not sure of |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Greg Studer | Assignee: | Backlog - Query Integration |
| Resolution: | Unresolved | Votes: | 22 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Query Integration
|
||||||||
| Participants: | |||||||||
| Description |
|
Allow reordering the criteria for the 2d index type, so the geo index can be used over subsets of the btree after some other criteria is chosen. example : coll.find({ tag : "a", loc : { $within : {...}} }) |
| Comments |
| Comment by Nelson LEVERT [ 03/Jun/13 ] |
|
Any update on this ? |
| Comment by hari.khalsa@10gen.com [ 08/Jan/13 ] |
|
Arbitrary ordering of geo and non-geo indexed fields is supported in the upcoming 2dsphere index type. See |
| Comment by Morgan Wu [ 07/Jan/13 ] |
|
I have the same question, my app is almost ready except LBS part, and I'm waiting for this feature. Anyone can give some news on it? Thanks. |
| Comment by Mikael Syska [ 06/Jan/13 ] |
|
This issue have had the "planned but not scheduled" since "Nov 19 2011 10:17:15 PM UTC". Are there any near future plans for this? |
| Comment by steven winner [ 03/Dec/12 ] |
|
To use geo searching properly, this is something that needs to be done. |
| Comment by Piotr Tomasik [ 18/May/12 ] |
|
This would be a very useful feature. |
| Comment by Eliot Horowitz (Inactive) [ 05/Apr/12 ] |
|
Just a note, in many cases this would be useful a haystack index would also be useful. |
| Comment by Robert La Ferla [ 04/Apr/12 ] |
|
This is perhaps the single-most important feature we need in Mongo. |
| Comment by Vladimir [ 04/Apr/12 ] |
|
This one will be very helpful. I didn't notice "Limits in geospatial queries are always applied to the geospatial component first" and now this breaks whole app logic. Really awaiting for fixes. |
| Comment by Mikael Syska [ 19/Nov/11 ] |
|
This will be a awesome feature for me. |