-
Type: Bug
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Catalog and Routing
-
ALL
As the title implies we only establish a consistent collection on the main namespace. On secondary namespaces we do not do anything else.
This affects SBE since they later perform a raw CollectionCatalog lookup on the secondary collection, which can return a Collection instance out of sync with the underlying WT snapshot.
- is related to
-
SERVER-91299 Refresh MultiCollectionAccessor after doing multi-planning
- Closed