-
Type:
Task
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Catalog and Routing
-
Fully Compatible
-
CAR Team 2025-04-14, CAR Team 2025-04-28
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
SERVER-75919 introduced the useClusterTransaction parameter to the sharding_ddl_util methods supported by the internal transactions API, together with an assertion to signal clients that were attempting to perform transaction write statements to the config server could without involving cluster ServiceEntryPoint.
Nevertheless, such a logic does not appear to bring any value today and it could be dropped, since useClusterTransaction:
- is set to true by any client of sharding_ddl_util (so that the tassert is always avoided)
- is not consumed anywhere else.
- related to
-
SERVER-75919 Investigate if runTransactionOnShardingCatalog should always use cluster transaction API
-
- Closed
-