-
Type: Improvement
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Aggregation Framework
-
None
-
Minor Change
-
v4.0
-
Query 2018-12-17, Query 2018-12-31, Query 2019-01-14, Query 2019-01-28, Query 2019-02-11
For example, this pipeline:
db.x.watch([{$replaceRoot: {newRoot: "$fullDocument"}}])
Such a pipeline is incompatible with the drivers protocol, and will fail to resume in the face of a network outage. It is not intended to be supported, so we should ban it to provide a more predictable failure scenario. Now that we have completed SERVER-35904, it shouldn't be very difficult to verify the _id is preserved by the pipeline.
- is depended on by
-
JAVA-2828 ChangeStreamIterable withDocumentClass throws exception because convertResultsCallback looks for resumeToken
- Closed
-
SERVER-38414 Upgrade/Downgrade testing for change stream high water mark
- Closed
-
SERVER-38408 Return postBatchResumeToken from all mongoD change streams
- Closed
- is related to
-
JAVA-3163 Re-enable the 'should throw if the _id field is projected out' changestream test for sharded clusters
- Closed
- related to
-
PHPLIB-446 Skip tests that modify resume token for server 4.1.8+
- Closed
-
SERVER-37669 Allow change streams to project out the resume token
- Backlog