-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Fully Compatible
-
Repl 2017-08-21, Repl 2017-09-11, Repl 2017-10-02, Repl 2017-10-23
The streams should be merged in order of the 'resumeToken' field of the change notification entries
- depends on
-
SERVER-29929 Report highest observed cluster time from change stream on each shard
- Closed
-
SERVER-22760 Sharded aggregation pipelines which involve taking a simple union should merge on mongos
- Closed
-
SERVER-30704 Use the AsyncResultsMerger to merge results from aggregation on mongos
- Closed
- is duplicated by
-
SERVER-30198 Support resumeAfter option to $changeNotification in sharded clusters
- Closed
-
SERVER-31179 Make sure change streams on sharded collections are unversioned and target all shards
- Closed
-
SERVER-29604 Error when resuming change notifications through mongos if there's no exact match on the ResumeToken from any shard
- Closed
- related to
-
SERVER-43500 Complete TODO listed in SERVER-29141
- Closed
-
SERVER-44220 Complete TODO listed in SERVER-29141
- Closed