Details
-
Task
-
Resolution: Fixed
-
Major - P3
-
None
-
None
-
None
-
Fully Compatible
-
Sharding EMEA 2023-05-29
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.