-
Type: Bug
-
Resolution: Works as Designed
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
ALL
-
v7.1, v7.0
-
CAR Team 2023-11-13, CAR Team 2023-11-27
Say we rename a collection a collection and the rename has only been applied to a minority of nodes in a replica set. That is, the majority timestamp hasn't yet advanced.
If a user were to perform $listCatalog targeting the old collection name with majority readConcern then the aggregation will fail since it is now checking against the latest version of the catalog instead of respecting the read concern.
- is caused by
-
SERVER-81028 Incorrect $listCatalog behavior in presence of a concurrent collection rename in v7.0
- Closed