-
Type:
Task
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Catalog and Routing
-
Fully Compatible
-
CAR Team 2025-04-14, CAR Team 2025-04-28, CAR Team 2025-05-12
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
The DatabaseShardingState interface should only expose virtual getters, while DatabaseShardingRuntime will implement methods and expose setters as well, clearly dividing read-only access from modifiable logic.
Following the modularization effort, the public interface should only be consumed by the Shard Role API and the private one by the DDLs, OpObservers and Sharding Recovery services.
- is depended on by
-
SERVER-104499 Evaluate whether the DDL lock manager is an internal CAR-only implementation detail or a public feature
-
- In Progress
-
-
SERVER-104498 Do not expose internal attributes like dbName, dbVersion, and dbPrimaryShard in DatabaseShardingState
-
- Closed
-
- related to
-
SERVER-104498 Do not expose internal attributes like dbName, dbVersion, and dbPrimaryShard in DatabaseShardingState
-
- Closed
-
- split from
-
SERVER-100711 Introduce a new class for maintaining DSS/CSS caches
-
- Closed
-