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:
- Preferred: find({geo: {$geoWithin: ...}}, {dist: {$meta: "geoNearDistance"}}).sort({dist: {$meta: "geoNearDistance"}})
- Not preferred: find({geo: {$nearSphere: ...}})
- is related to
-
SERVER-17920 InternalError when using geoNear $meta projections with non-geo data
-
- Closed
-
- related to
-
-
- Closed
-
-
-
- Closed
-