[SERVER-66872] Re-enable multi-database access in AutoGetDb Created: 31/May/22  Updated: 06/Dec/22  Resolved: 08/Jul/22

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

Type: Task Priority: Major - P3
Reporter: Dianna Hohensee (Inactive) Assignee: Backlog - Storage Execution Team
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-66899 Support multi-collection shardVersion... Closed
Duplicate
Assigned Teams:
Storage Execution
Participants:

 Description   

This was disabled in SERVER-64121 because the sharding protocol can't support checking whether or not a collection is sharded without first checking the dbVersion, which is also not supported by the sharding protocol for more than one database.

The work for the sharding protocol changes are not scheduled. This is a placeholder for someday, with a TODO reference in the code, instead of ripping out support from AutoGetDb.



 Comments   
Comment by Kaloian Manassiev [ 08/Jul/22 ]

Multiple DB/Collection locking at the level of the AutoGetters is not the right way to expose the semantics of this functionality. I am closing this ticket in lieu of PM-2144 and specifically the local programming API as is being designed in WRITING-11352.

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