Loading...

XML

Word

Printable

JSON

Type: Improvement
Resolution: Fixed
Priority: Critical - P2
Fix Version/s: 8.1.0-rc0, 8.0.5, 7.0.18, 6.0.24
Affects Version/s: None
Component/s: Change streams
Labels:
- auto-reverted

Assigned Teams:

Query Execution
Backwards Compatibility:
Fully Compatible
Backport Requested:

v8.0, v7.0, v6.0
Sprint:
QE 2024-10-28, QE 2024-11-11, QE 2024-11-25, QE 2024-12-09
Linked BF Score:
200
Confidence Status:
None
Work Order:
0

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name:
None
Goal Link:
None

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

Closed

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

Closed

Avoid dropping database in change_stream_null_existence_eq_rewrite_test.js test

SERVER-97682

Closed

Denis Grebennicov

8.1.0-rc0

Assignee:: Denis Grebennicov
Reporter:: Sebastien Mendez
Participants:: Denis Grebennicov, Githook User, Sebastien Mendez
Votes:: 0 Vote for this issue
Watchers:: 8 Start watching this issue

Created:: Oct 18 2024 08:55:25 AM UTC
Updated:: May 08 2025 07:06:53 AM UTC
Resolved:: Nov 27 2024 02:26:29 PM UTC
Confidence Status Last Update:: 22/Oct/24 8:52 AM

Details

Description

Attachments

Issue Links

Sub-Tasks

Activity

People

Dates