-
Type:
Task
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Query Integration
-
Fully Compatible
-
200
-
None
-
3
-
TBD
-
None
-
None
-
None
-
None
-
None
-
None
-
None
While working on SERVER-103281 I found that DocumentSourceGeoNear::validatePipelinePosition() complained for some reason. Looking at the logs I think the pipeline that was being validated didn't have the $geoNear in it, so it might have to do with the splitting (this only happened in sharded scenarios).
Also noteworthy, such a command on a sharded collection fails even though the explain works, while on a sharded clusted with an unsharded collection the command works but the explain fails.
- is depended on by
-
SERVER-103998 Allow $rankFusion inside a $unionWith/$lookup on a view
-
- Closed
-
-
SERVER-106028 Ensure a $rankFusion inside a $unionWith/$lookup, with top level aggregation on a view works and is tested
-
- Closed
-
-
SERVER-106129 Add tests for a $rankFusion (with non-search input pipelines) running on a view containing a search stage
-
- Closed
-
- is duplicated by
-
SERVER-107094 Remove addResolvedNamespace call for non rankFusion pipelines
-
- Closed
-
- is related to
-
SERVER-103281 Enable and test running $rankFusion on a view with non-search input pipelines
-
- Closed
-