Currently, attempting to run a $lookup sub-pipeline with a geoNear within it will cause DocumentSourceGeoNear's getNext to be called, triggering an error.
Part of this ticket will involve reactivating jstests/aggregation/sources/geonear/requires_geo_index.js and jstests/aggregation/sources/lookup/lookup_subpipeline_geonear.js for passthroughs with sharded collections.
It will also involve changing the internal error code assertion #50144 to a MONGO_UNNREACHABLE.
- depends on
-
SERVER-38716 fix $geoNear and $text within $lookup sub-pipeline
-
- Closed
-
-
SERVER-38728 Allow pipeline with $lookup into a sharded collection to run on mongod
-
- Closed
-