[SERVER-36275] Support sending non-contiguous ranges to the same shard in $exchange Created: 25/Jul/18 Updated: 29/Oct/23 Resolved: 27/Jul/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Aggregation Framework, Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.2 |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Charlie Swanson | Assignee: | Martin Neupauer |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Sprint: | Query 2018-07-30, Query 2018-08-13 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
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. |
| Comments |
| Comment by Githook User [ 27/Jul/18 ] |
|
Author: {'name': 'Martin Neupauer', 'email': 'martin.neupauer@mongodb.com', 'username': 'MartinNeupauer'}Message: |