[SERVER-72050] Investigate changing CachedCollectionProperties to be keyed with NamespaceString object Created: 12/Dec/22  Updated: 23/Mar/23  Resolved: 23/Mar/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Sophia Tan Assignee: Sophia Tan
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-74795 Change CachedCollectionProperties to ... Closed
Assigned Teams:
Serverless
Backwards Compatibility: Fully Compatible
Sprint: Server Serverless 2023-03-06, Server Serverless 2023-03-20, Server Serverless 2023-04-03
Participants:

 Description   

Today, collection properties which are relevant for oplog application are cached in memory and can be retrieved with string ns. There some potential issues:

  • the tenant id is dropped off.
  • the code will not keep working once NamespaceString(StringData ns) constructor is removed by SERVER-65920.

In this ticket, we will investigate if it makes sense to leave it as a StringMap for some optimization reason or not. If we decide to leave it as a StringMap, we should think about  to pass in tenant prefixed ns string and deserialize it correctly. 


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