Description:

As part of this ticket we also added some fields which are present only for change stream documents generated from an operation run inside of a transaction.

The fields are:
"txnNumber" (the transaction number)
"lsid" (which session the transaction was run in)

Scope of changes:

• reference/change-events
• changeStreams
• 4.0 in change streams section

• For now, won't blurbing in txn docs for this use case as the info seems more relevant in change streams section.

Impact to other docs outside of this product:

MVP:

Resources:

Engineering Ticket Description:

The current resume token format is not sufficient to impose a total ordering on all changes once we unpack operations from within an applyOps array into one change each. Changes within an applyOps can all have identical resume tokens if there are multiple updates to the same document.