-
Type: Bug
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Aggregation Framework
-
Query Execution
-
ALL
If the user opens a change stream at a point in the future, and then adds a new shard before the cluster reaches that time, then the stream on the new shard will be opened at the current clusterTime. The stream will therefore be able to see events on the new shard even if these events precede the user's requested startAtOperationTime. The postBatchResumeToken returned to the client will also revert back-in-time to the current clusterTime.
- is related to
-
SERVER-44039 Improve $changeStream handling of cluster topology changes
- Backlog