[SERVER-77125] Avoid unnecessary construction of NamespaceString on collection acquisitions Created: 15/May/23 Updated: 29/Oct/23 Resolved: 16/May/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.1.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Jordi Serra Torrens | Assignee: | Jordi Serra Torrens |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Sharding EMEA 2023-05-29 |
| Participants: |
| Description |
|
Due to the ambiguity between these two overloads of CollectionAcquisitionRequest (by nss and by nssOrUuid), callers had to explicitly cast or unnecessarily construct a NamespaceString object when they acquire a collection given a NamespaceString::ConstantProxy (e.g. here). It should be enough to keep the by-nssOrUuid constructor, since the two are actually overlapping. |
| Comments |
| Comment by Githook User [ 16/May/23 ] |
|
Author: {'name': 'Jordi Serra Torrens', 'email': 'jordi.serra-torrens@mongodb.com', 'username': 'jordist'}Message: |