-
Type: Improvement
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Aggregation Framework
-
None
-
Fully Compatible
-
Query 2018-03-12, Query 2018-03-26, Query 2018-07-02, Query 2018-07-16, Query 2018-07-30, Query 2018-08-13, Query 2018-08-27
-
75
This can be done as follow-on work after SERVER-24978, and will remove a layer of indirection between the pipeline executing on mongos and the AsyncResultsMerger. Today, the pipeline is attached via a DocumentSourceRouterAdapter which draws results from a RouterStageMerge which draws results from an AsyncResultsMerger.
Once the $mergeCursors stage is using the AsyncResultsMerger, we can collapse that picture and eliminate the DocumentSourceRouterAdapter and RouterStageMerge.
- depends on
-
SERVER-24978 Second batches in aggregation framework are asked synchronously
- Closed
- is depended on by
-
SERVER-35581 Don't mandate the use of "distanceField" in $geoNear
- Backlog
- related to
-
SERVER-36781 Coverity analysis defect 104978: Uninitialized scalar field
- Closed
-
SERVER-34009 Remove support for 3.6 $mergeCursors serialization format
- Closed