[SERVER-17929] Add full query support for $meta values geoNearDistance/geoNearPoint Created: 08/Apr/15 Updated: 28/Dec/23 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | Geo, Querying |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | J Rassi | Assignee: | Backlog - Query Integration |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | qi-geo | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Assigned Teams: |
Query Integration
|
||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
The $meta values "geoNearDistance"/"geoNearPoint" should be given full query support. Exposing "geoNearDistance" to users will allow them to get off of the $near/$nearSphere query operators, which suffer from no real query planner support and poor semantics. For example:
|
| Comments |
| Comment by Siyuan Zhou [ 15/Apr/15 ] |
|
If $near is considered as projection and sorting explicitly, we don't have to enforce the use of geo index if another normal index can be more efficient, see |