[sakthivelmanii]

Problem

• When location-aware routing is enabled, BeginTransactionRequest calls with TransactionOptions.PartitionedDml recorded transaction affinity in KeyAwareChannel, leaking affinity entries for 10 minutes because Partitioned DML transactions are never committed or rolled back.
• Subsequent Partitioned DML ExecuteSql and ExecuteStreamingSql calls entered KeyAwareChannel via partitionedDmlStub, causing routeFromRequest(ExecuteSqlRequest.Builder) to attach a RoutingHint and route the statement to the server fastpath, which rejects Partitioned DML transactions with INVALID_ARGUMENT: PartitionedDml Transactions may only be used to execute DML statements.

Solution

• Configure GapicSpannerRpc's partitionedDmlStub with a ClientContext backed directly by KeyAwareChannel.defaultChannel() when KeyAwareChannel is active so Partitioned DML ExecuteSql and ExecuteStreamingSql requests bypass KeyAwareChannel and always use the default channel without routing hints.
• Update KeyAwareChannel so BeginTransactionRequest and inline TransactionSelector.begin calls with TransactionOptions.PartitionedDml set shouldRecordTransactionAffinity = false.
• Add unit tests in GapicSpannerRpcTest and KeyAwareChannelTest verifying that Partitioned DML requests bypass KeyAwareChannel and do not record transaction affinity.

[sakthivelmanii]

/gemini review

[gemini-code-assist]

Code Review

This pull request ensures that routing hints are never attached to Partitioned DML requests in KeyAwareChannel. It introduces a cache to track Partitioned DML transaction IDs and bypasses attaching routing hints for these transactions, routing them to the affinity or default endpoint instead. A unit test has been added to verify this behavior. I have no feedback to provide.

[gemini-code-assist]

Code Review

This pull request ensures that Partitioned DML transactions do not carry routing hints by introducing a cache to track Partitioned DML transaction IDs in KeyAwareChannel. Requests for these transactions are routed without a routing hint, preventing them from being executed on the fastpath which does not support Partitioned DML. A unit test has been added to verify this behavior. I have no feedback to provide on these changes.

[sakthivelmanii]

/gemini review

[gemini-code-assist]

Code Review

This pull request ensures that Partitioned DML transactions and operations bypass the KeyAwareChannel routing and affinity mechanisms, executing directly on the default channel. It achieves this by configuring the partitionedDmlStub with a ClientContext using the default transport channel and updating KeyAwareChannel to disable transaction affinity tracking when Partitioned DML options are present. Comprehensive unit and integration tests have been added to verify these changes. I have no additional feedback to provide as the implementation is clean and well-tested.