-
Type:
Improvement
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: Change streams
-
None
-
Query Execution
-
Minor Change
-
QE 2026-05-11
-
None
-
None
-
None
-
None
-
None
-
None
-
None
The undocumented {showMigrationEvents: true} option to $changeStreams causes oplog entries with {fromMigrate: true} to be returned. This behavior was initially introduced for Atlas Search as part of SERVER-38682. One idea for detecting when mongosync would be impacted by REP-4188 was to open a {showMigrationEvents: true} change stream and detect the range deleter running from its delete change events. Unfortunately the {fromMigrate: true} designation is not preserved between the oplog entry and the change event and so there is no way to distinguish application client deletes from range deleter deletes. While a different approach will ultimately be taken for mongosync, we should improve the behavior for the {showMigrationEvents: true} option such that it preserves more information from the underlying oplog entry.
- causes
-
SERVER-126035 Robustify condition for emission of 'fromMigrate' field
-
- Closed
-
- is depended on by
-
TOOLS-4198 Investigate changes in SERVER-88167: Expose information about change event being from a migration event when change streams run with showMigrationEvents:true
-
- Needs Discussion
-
- is related to
-
-
- Closed
-
- related to
-
SERVER-107688 The op entries generated by the data-cloning phase of a cross-DB renameCollection request should not be visible to change stream readers
-
- Backlog
-
-
-
- Needs Scheduling
-