-
Type:
Task
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Catalog and Routing
-
Fully Compatible
-
CAR Team 2026-06-08, CAR Team 2026-06-22
-
None
-
None
-
None
-
None
-
None
-
None
-
None
The AsyncRequestsSender is used extensively both for DDL and for query routing. A lot of places use the request object from the AsyncRequestsSender even if they use something else (like the MultiStatementTransactionRequestsSender) for actually executing the requests.
Now that the dbInfo is using a ShardRef, we can start piping the shardRef through the in memory structures and be able to test that it is working. In this first ticket, we will also need to update the ShardRegistry's getShard to work with shardRef.
- is depended on by
-
SERVER-128062 Update sharding ddl utils to use ShardRef and ShardHandle
-
- Backlog
-
-
SERVER-128424 Update AsyncRequestSender response users to use the correct shard identifier
-
- Closed
-