Details
-
Improvement
-
Resolution: Fixed
-
Major - P3
-
None
-
None
Description
Description
Currently the documentation for clusterTime in a change stream event says:
For events that happened as part of a multi-document transaction, the associated change stream notifications will have the same clusterTime value, namely the time when the transaction was committed
While this is still factually correct in MongoDB 4.2, it implies something that may not be true: that two events with the same clusterTime ALWAYS are part of the same transaction. As schwerin pointed out to me, two transactions that are not causally consistent with each other, and that execute on two different shards, could end up with the same clusterTime for their associated change stream events.
Scope of changes
- Update description of clusterTime on https://docs.mongodb.com/manual/reference/change-events/
Impact to Other Docs
MVP (Work and Date)
Resources (Scope or Design Docs, Invision, etc.)
Attachments
Issue Links
- related to
-
JAVA-3225 ChangeStreamDocument does not have getters for txnNumber and lsid fields
-
- Closed
-