Loading...

XML

Word

Printable

JSON

Type: Task
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-08-13, Query 2018-08-27, Query 2018-09-10
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

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

Once we can detect when this is possible, and can output multiple cursors from mongod, this work is to consume those cursors, re-shuffle them, and send them to the appropriate shards, then add a step to merge all those cursors back together.

causes

SERVER-81132 Avoid scanning entire routing table during $merge stage planning

Backlog

depends on

SERVER-35899 Have mongos produce an aggregation plan that correctly uses an $exchange

Closed

SERVER-35904 Implement logic to detect if merging half of pipeline conserves but possibly renames the shard key

Closed

is depended on by

SERVER-36113 Add ability to perform $exchange when shard key is hashed

Closed

SERVER-36279 Change the explain format for sharded aggregations to accomodate $exchange

Closed

SERVER-36533 Report execution stats for $exchange in sharded aggregation explains

Backlog

is duplicated by

SERVER-35974 Create a DocumentSourceExchangeConsumer

Closed

(1 is depended on by, 1 is duplicated by)

Assignee:: Martin Neupauer (Inactive)
Reporter:: Charlie Swanson
Participants:: Charlie Swanson, Githook User, Martin Neupauer
Votes:: 0 Vote for this issue
Watchers:: 6 Start watching this issue

Created:: Jun 28 2018 10:10:20 PM UTC
Updated:: Oct 29 2023 10:30:13 PM UTC
Resolved:: Aug 30 2018 06:51:57 PM UTC

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates