[SERVER-73275] Use openCollection with NamespaceOrUUID from lock-free read path when appropriate Created: 24/Jan/23  Updated: 27/Oct/23  Resolved: 26/Jan/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Matthew Saltz (Inactive) Assignee: Matthew Saltz (Inactive)
Resolution: Gone away Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-73224 Reads during concurrent rename may ca... Closed
depends on SERVER-68271 Trigger Collection instantiation when... Closed
Related
Operating System: ALL
Sprint: Execution Team 2023-02-06
Participants:
Linked BF Score: 5

 Description   

The lock-free read path (AutoGetCollectionForReadLockFree) always calls CollectionCatalog::openCollection passing in a NamespaceString, but should instead pass in a UUID when one is provided by the user of AutoGetCollectionForReadLockFree.

This ticket should also re-enable find_by_uuid_and_rename.js when the PointInTimeCatalogLookups feature is enabled, and also remove the multiversion_incompatible tag from it.



 Comments   
Comment by Matthew Saltz (Inactive) [ 26/Jan/23 ]

Done as part of SERVER-68271

Generated at Thu Feb 08 06:24:11 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.