The spec change in DRIVERS-595 requires that drivers provide an API for exposing the current resume token, which may come from a change document or a postBatchResumeToken field. DRIVERS-634 builds upon that issue and adds more clarity around which value should be returned (and used for resuming).
In DRIVERS-436, drivers added an example for accessing the resume token (example #3), which is published within https://docs.mongodb.com/manual/changeStreams/#resume-a-change-stream. This example should be updated to use whatever new API was introduced for 4.2 drivers in DRIVERS-595.
- depends on
-
CDRIVER-3207 Update change stream docs example for resume token access
- Closed
-
CSHARP-2651 Update change stream docs example for resume token access
- Closed
-
CXX-1794 Update change stream docs example for resume token access
- Closed
-
GODRIVER-1164 Update change stream docs example for resume token access
- Closed
-
JAVA-3337 Update change stream docs example for resume token access
- Closed
-
MOTOR-355 Update change stream docs example for resume token access
- Closed
-
NODE-2028 Update change stream docs example for resume token access
- Closed
-
PHPLIB-450 Update change stream docs example for resume token access
- Closed
-
PYTHON-1885 Update change stream docs example for resume token access
- Closed
-
RUBY-1856 Update change stream docs example for resume token access
- Closed
- is related to
-
DRIVERS-595 Support postBatchResumeToken in change streams
- Development Complete
-
DRIVERS-436 Add pipeline stage to ChangeStreams example for Docs
- Closed
-
DRIVERS-634 Clarify resume token used in resuming and getResumeToken
- Closed