[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: |
|
||||||||
| 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:
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. |