Details
-
Bug
-
Resolution: Fixed
-
Major - P3
-
None
-
None
-
None
-
Fully Compatible
-
ALL
-
Execution Team 2023-02-20, Execution Team 2023-02-06
-
5
Description
We resolve the UUID to a NamespaceString that is then used for the rest of the read setup.
However, when there is a concurrent rename that is committed to the storage engine but not to the in-memory catalog we wrongly report this as the collection not existing.
We need to perform openCollection with a UUID in this case to be correct.
Attachments
Issue Links
- is depended on by
-
SERVER-73275 Use openCollection with NamespaceOrUUID from lock-free read path when appropriate
-
- Closed
-