-
Type: Improvement
-
Resolution: Unresolved
-
Priority: Critical - P2
-
None
-
Affects Version/s: None
-
Component/s: Change streams
-
None
-
Query Execution
-
v8.0, v7.0, v6.0
-
QE 2024-10-28, QE 2024-11-11, QE 2024-11-25
-
200
After a collection is renamed, some other collection with the old name may be present. When this happens, currently it's possible that changestream look up a document in this new collection, rather than in the collection that was renamed.
This can cause the MongoSync verifier to falsely say documents match when they do not.
We need an internal flag to enforce updateLookup to only return a document from the correct collection.
- related to
-
SERVER-96465 Change stream updateLookup is not returning documents when reading before reshardCollection even happened
- Needs Scheduling
-
SERVER-93070 updateLookup should use the best identifier between the collection UUID and name
- Open
-
SERVER-96463 Avoid code duplicate in preparePipelineForExecution() and targetShardsAndAddMergeCursors() when routing pipelines
- Needs Scheduling