-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Aggregation Framework
-
None
-
Fully Compatible
-
Query 2018-08-13, Query 2018-08-27, Query 2018-09-10
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