Details
-
Task
-
Resolution: Duplicate
-
Major - P3
-
None
-
None
-
None
Description
Description:
This was a departure from the original syntax laid out in the scope/design. I'll update the scope/design document to account for this change, but just in case here's the history.
Scope of changes:
Impact to other docs outside of this product:
MVP:
Resources:
Engineering Ticket Description:
In 4.0, we will be allowing users to specify a startAtClusterTime option. Currently, the server expects the option to be a BSON document of the form:
{ ts: Timestamp }
|
This naming not intuitive, as a clusterTime object (as defined in server response $clusterTime.clusterTime) does not conform to this format.
We should either modify the startAtClusterTime field to expect a raw BSON timestamp, or choose a more intuitive name for the field.
Attachments
Issue Links
- documents
-
SERVER-34818 changeStream option startAtClusterTime should be a raw BSON Timestamp
-
- Closed
-
- duplicates
-
DOCS-11561 Docs for SERVER-33818: Add 'startAtOperationTime' as an option in $changeStream
-
- Closed
-
- is related to
-
DOCS-11438 Docs for SERVER-33778: Remove change_stream_remove_shard.js
-
- Closed
-
-
DOCS-11760 Docs for SERVER-34314: Ensure change stream can resume between entries in applyOps entry
-
- Closed
-
- related to
-
DOCS-11561 Docs for SERVER-33818: Add 'startAtOperationTime' as an option in $changeStream
-
- Closed
-