[SERVER-67783] Remove usages of AutoGetCollection::getDb related to makeUniqueCollectionNamespace Created: 05/Jul/22 Updated: 29/Oct/23 Resolved: 11/Jul/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 6.1.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Kaloian Manassiev | Assignee: | Kaloian Manassiev |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | PM-2144-Milestone-0 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Sharding EMEA 2022-07-11 |
| Participants: |
| Description |
|
With the separation of the Collection catalog to no longer be subordinate to the Database one (DatabaseHolder), the Database object no longer serves any purpose other than to track some sharding state. Because of this, references to ::getDb no longer make sense and should be removed. This ticket is about the callers to makeUniqueCollectionNamespace. |
| Comments |
| Comment by Githook User [ 08/Jul/22 ] |
|
Author: {'name': 'Kaloian Manassiev', 'email': 'kaloian.manassiev@mongodb.com', 'username': 'kaloianm'}Message: |