-
Type: New Feature
-
Resolution: Done
-
Priority: Major - P3
-
None
-
Component/s: Change Streams
-
None
Lead:
POCs:
Summary:
The startAfter option is being added in order to convey intent to users about the creation of a new change stream based on an pre-existing resume token from a collection that has been invalidated. Creating a change stream with the startAfter parameter specified in the $changeStream stage will open a cursor opportunistically, and wait for the collection to be come available. In this sense, startAfter provides a way for users to never miss a single event.
Final Specification:
https://github.com/mongodb/specifications/commit/830715cd8a84da9c5582617a3e3a7d40171aa5f8
- depends on
-
CDRIVER-2925 Support 'startAfter' option to the $changeStream stage
- Closed
-
CSHARP-2483 Support 'startAfter' option to the $changeStream stage
- Closed
-
CXX-1715 Support 'startAfter' option to the $changeStream stage
- Closed
-
GODRIVER-765 Support 'startAfter' option to the $changeStream stage
- Closed
-
JAVA-3139 Support 'startAfter' option to the $changeStream stage
- Closed
-
MOTOR-297 Support 'startAfter' option to the $changeStream stage
- Closed
-
NODE-1824 Support 'startAfter' option to the $changeStream stage
- Closed
-
PHPLIB-407 Support 'startAfter' option to the $changeStream stage
- Closed
-
PYTHON-1720 Support 'startAfter' option to the $changeStream stage
- Closed
-
RUST-113 Support 'startAfter' option to the $changeStream stage
- Closed
-
SERVER-35030 Add 'startAfter' option to the $changeStream stage
- Closed
-
RUBY-1668 Support 'startAfter' option to the $changeStream stage
- Closed
- is duplicated by
-
DRIVERS-593 Add support for 'startAfter' option to the $changeStream stage
- Closed