-
Type: Improvement
-
Resolution: Unresolved
-
Priority: Minor - P4
-
None
-
Affects Version/s: None
-
Component/s: Aggregation Framework
-
Query Integration
-
Minor Change
The $geoNear stage requires that "distanceField" is specified. Presumably, this was required to allow $geoNear to work in a sharded cluster, as mongos must take the results from each shard and merge them in ascending order of distance. However, users that aren't interested in the actual distance will have to project out the field in their results.
When SERVER-35043 is complete, DocumentSourceGeoNearCursor could ensure that the sort key is set to be the computed distance without requiring that "distanceField" is actually added to the output.
- depends on
-
SERVER-33323 Refactor $mergeCursors stage to allow it to be used to merge cursors on mongos
- Closed
- has to be done after
-
SERVER-35043 Remove geoNear command
- Closed
- related to
-
SERVER-58443 Allow $near/$nearSphere on a view
- Backlog
-
SERVER-93613 Investigate if we should remove support for sorting by {$meta: "geoNearDistance"}
- Backlog