-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Serverless
-
Fully Compatible
-
Server Serverless 2023-05-29, Server Serverless 2023-06-12, Server Serverless 2023-06-26, Server Serverless 2023-07-10, Server Serverless 2023-07-24
-
5
In order to ensure NamespaceString is always serialized correctly, we will create context specific toString methods on NamespaceString and NamespaceStringUtil, and remove any default serialization behavior.
- depends on
-
SERVER-73115 Always include tenant in collection name attributes in log lines
- Closed
-
SERVER-74463 Change OplogInterfaceRemote and RollbackSource to take in NamespaceString
- Closed
-
SERVER-74486 Always include tenant in collection name attributes in error messages
- Closed
-
SERVER-75276 writeConflictRetry should properly be using a NamespaceString instead of a StringData
- Closed
-
SERVER-77396 Refactor some of the concurrency exception util method
- Closed
-
SERVER-78574 Refactor RecordStore::ns to return a NamespaceString object
- Closed
-
SERVER-78577 CollectionScanNode to store a NamespaceString for 'name' attribute
- Closed
- is related to
-
SERVER-77920 Investigate / Cleanup `_isSecondaryQuery` from dbclient_rs
- Open
-
SERVER-77329 CommandHelpers::resourcePatternForNamespace to use a NamespaceString
- Closed
-
SERVER-78001 plan_cache_commands::canonicalize to pass NamespaceString
- Closed
-
SERVER-78004 Top::record to take in a NamespaceString object
- Closed