[SERVER-83797] Introduce DatabaseNameUtil (de)serialize functions for non idl generated code Created: 01/Dec/23  Updated: 07/Feb/24

Status: In Code Review
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Mathis Bessa Assignee: Mathis Bessa
Resolution: Unresolved Votes: 0
Labels: ntdi_code_quality, ntdi_must_have
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-84355 Resolve Circular Dependency in order ... Closed
is depended on by SERVER-86352 Replace calls to DatabaseNameUtil (de... Needs Scheduling
Related
related to SERVER-82352 Replace tenantId and SerializationCon... Closed
is related to SERVER-85476 Simplify DatabaseNameUtil API Closed
Sprint: Service Arch 2024-01-08, Service Arch 2024-01-22, Service Arch 2024-02-05, Service Arch 2024-02-19
Participants:
Story Points: 8

 Description   

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. 

 


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