From 5f3e258f4d3de1728879709162cd8a690a361f2e Mon Sep 17 00:00:00 2001 From: Andrew Feierabend Date: Wed, 13 Jan 2021 15:12:31 -0500 Subject: [PATCH] DOCSP-13944 clarify _id resumeToken definition for change streams --- source/reference/change-events.txt | 14 ++++++++++---- 1 file changed, 10 insertions(+), 4 deletions(-) diff --git a/source/reference/change-events.txt b/source/reference/change-events.txt index 587f3e896fd..c05d2394b45 100644 --- a/source/reference/change-events.txt +++ b/source/reference/change-events.txt @@ -62,8 +62,10 @@ following table describes each field in the change stream response document: - document - .. _change-stream-event-id: - Metadata related to the operation. Acts as the ``resumeToken`` + A :term:`BSON` object which serves as an identifier for the + change stream event. This value is used as the ``resumeToken`` for the ``resumeAfter`` parameter when resuming a change stream. + The ``_id`` object has the following form: .. code-block:: none @@ -72,9 +74,13 @@ following table describes each field in the change stream response document: } The ``_data`` type depends on the MongoDB versions - and, in some cases, the feature compatibility version (fcv) at - the time of the change stream's opening/resumption. For details, - see :ref:`change-stream-resume-token`. + and, in some cases, the :ref:`feature compatibility version (fCV) + ` at the time of the change stream's + opening/resumption. See :ref:`change-stream-resume-token` for the + full list of ``_data`` types. + + See :ref:`change-stream-resume` for an example of resuming a + change stream by ``resumeToken``. * - ``operationType`` - string