[SERVER-31179] Make sure change streams on sharded collections are unversioned and target all shards Created: 20/Sep/17 Updated: 02/Oct/17 Resolved: 02/Oct/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying, Replication, Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Spencer Brody (Inactive) | Assignee: | Bernard Gorman |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Repl 2017-10-02 | ||||||||
| Participants: | |||||||||
| Description |
|
We can't properly target change streams on sharded collections currently (until we have multi-version routing tables), so we should send change streams on sharded collections to all shards and we should opt-out of the shard versioning protocol. |
| Comments |
| Comment by Bernard Gorman [ 02/Oct/17 ] |
|
ian.whalen: I already took care of this in the sharded collections patch that I handed off to Charlie. Will mark as a duplicate of |
| Comment by Ian Whalen (Inactive) [ 02/Oct/17 ] |
|
bernard.gorman whose input is this waiting on? |