Loading...

XML

Word

Printable

JSON

Type: Improvement
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 4.1.3
Affects Version/s: None
Component/s: Aggregation Framework
Labels:
None

Backwards Compatibility:
Fully Compatible
Sprint:
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
Linked BF Score:
75
Confidence Status:
None
Work Order:
3

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name:
None
Goal Link:
None

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

Closed

related to

SERVER-36781 Coverity analysis defect 104978: Uninitialized scalar field

Closed

SERVER-34009 Remove support for 3.6 $mergeCursors serialization format

Closed

Assignee:: Charlie Swanson
Reporter:: Charlie Swanson
Participants:: Charlie Swanson, Githook User, Will Schultz
Votes:: 0 Vote for this issue
Watchers:: 7 Start watching this issue

Created:: Feb 14 2018 03:19:19 PM UTC
Updated:: Oct 29 2023 10:34:43 PM UTC
Resolved:: Aug 20 2018 07:08:02 PM UTC
Confidence Status Last Update:: 02/Jul/18 10:22 PM

Details

Description

Attachments

Issue Links

Activity

People

Dates