-
Type: Task
-
Resolution: Won't Do
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Service Arch
-
Service Arch 2024-01-08, Service Arch 2024-01-22, Service Arch 2024-02-05, Service Arch 2024-02-19, Service Arch 2024-03-04
-
8
We are currently transitioning to using a ValidatedTenancyScope as a source of truth in order to serialize / deserialize database names.
As part of SERVER-82352, we are changing the constructor to now pass in a ValidatedTenancyScope.
Because we are still serializing using a SerializationContext, we can not remove the SerializationContext as part of the constructor in the IDLParser
In this ticket, we should create Serialization / Deserialization for DatabaseNameUtil that takes in a ValidatedTenancyScope. The behavior should be identical to the way the SerializationContext does.
- depends on
-
SERVER-84355 Resolve Circular Dependency in order to use a ValidatedTenancyScope for (de)serialization
- Closed
- is depended on by
-
SERVER-86352 Replace calls to DatabaseNameUtil (de) serialize functions to not use SerializationContext
- Closed
- is related to
-
SERVER-85476 Simplify DatabaseNameUtil API
- Closed
- related to
-
SERVER-82352 Replace tenantId and SerializationContext with ValidatedTenancyScope in IDLParserContext constructor
- Closed