DOCS-15258 walltime change streams (#1197)

* DOCS-15258-walltime-change-streams

* DOCS-15258-walltime-change-streams

* DOCS-15258-walltime-change-streams

* DOCS-15258-walltime-change-streams

Co-authored-by: jason-price-mongodb <[email protected]>

Author: jason-price-mongodb

source/reference/change-events.txt

@@ -52,6 +52,7 @@ stream response document can have.
       "collectionUUID": <uuid>,
       "wallTime": <isodate>,
       "clusterTime" : <Timestamp>,
+      "wallTime" : <ISODate>,  // Added in MongoDB 6.0
       "txnNumber" : <NumberLong>,
       "lsid" : {
          "id" : <UUID>,
@@ -284,6 +285,15 @@ following table describes each field in the change stream response document:
 
        .. versionadded:: 4.0
 
+   * - ``wallTime``
+     - :term:`ISODate`
+     - The server date and time of the database operation. ``wallTime``
+       differs from ``clusterTime``:  ``clusterTime`` is the timestamp
+       from the oplog entry associated with the database operation
+       event.
+
+       .. versionadded:: 6.0
+
    * - ``txnNumber`` 
      - NumberLong
 
@@ -316,6 +326,7 @@ The following example illustrates an ``insert`` event:
       _id: { < Resume Token > },
       operationType: 'insert',
       clusterTime: <Timestamp>,
+      wallTime: <ISODate>,
       ns: {
          db: 'engineering', 
          coll: 'users'
@@ -351,6 +362,7 @@ The following example illustrates an ``update`` event:
       _id: { < Resume Token > },
       operationType: 'update',
       clusterTime: <Timestamp>,
+      wallTime: <ISODate>,
       ns: { 
          db: 'engineering', 
          coll: 'users'
@@ -379,6 +391,7 @@ opened with the ``fullDocument : updateLookup`` option:
       _id: { < Resume Token > },
       operationType: 'update',
       clusterTime: <Timestamp>,
+      wallTime: <ISODate>,
       ns: { 
          db: 'engineering', 
          coll: 'users'
@@ -426,6 +439,7 @@ The following example illustrates a ``replace`` event:
       _id: { < Resume Token > },
       operationType: 'replace',
       clusterTime: <Timestamp>,
+      wallTime: <ISODate>,
       ns: {
          db: 'engineering', 
          coll: 'users'
@@ -463,6 +477,7 @@ The following example illustrates a ``delete`` event:
       _id: { < Resume Token > },
       operationType: 'delete',
       clusterTime: <Timestamp>,
+      wallTime: <ISODate>,
       ns: {
          db: 'engineering',
          coll: 'users'
@@ -495,6 +510,7 @@ following example illustrates a ``drop`` event:
       _id: { < Resume Token > },
       operationType: 'drop',
       clusterTime: <Timestamp>,
+      wallTime: <ISODate>,
       ns: {
          db: 'engineering',
          coll: 'users'
@@ -520,6 +536,7 @@ illustrates a ``rename`` event:
       _id: { < Resume Token > },
       operationType: 'rename',
       clusterTime: <Timestamp>,
+      wallTime: <ISODate>,
       ns: {
          db: 'engineering',
          coll: 'users'
@@ -550,6 +567,7 @@ example illustrates a ``dropDatabase`` event:
       _id: { < Resume Token > },
       operationType: 'dropDatabase',
       clusterTime: <Timestamp>,
+      wallTime: <ISODate>,
       ns: {
          db: 'engineering'
       }
@@ -575,7 +593,8 @@ The following example illustrates an ``invalidate`` event:
    {
       _id: { < Resume Token > },
       operationType: 'invalidate',
-      clusterTime: <Timestamp>
+      clusterTime: <Timestamp>,
+      wallTime: <ISODate>
    }
 
 For change streams opened up against a collection, a

source/release-notes/6.0.txt

@@ -148,6 +148,10 @@ Change Streams
 
 .. include:: /includes/change-streams-optimization.rst
 
+Starting in MongoDB 6.0, the :ref:`change stream output
+<change-stream-output>` has a new ``wallTime`` field that contains the
+server date and time of the database operation.
+
 Cluster Administration
 ----------------------