-
Type:
New Feature
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: Aggregation Framework, Sharding
-
None
-
Fully Compatible
-
Query 2018-07-30, Query 2018-08-13
The initial implementation of the exchange operator supports a policy for distributed based on a set of boundaries of the shard key, but we need to support sending two separate ranges to the same shard, ideally without having separate consumers for each range on that shard. For example, if shard X owns the shard key ranges [0, 5) and [10, 20), the exchange producer should be able to send those values to that shard in a single output stream.
This should still work with an order preserving exchange as well.
- depends on
-
SERVER-35894 Create a $exchange producer stage
-
- Closed
-
- is depended on by
-
-
- Closed
-
-
-
- Closed
-