fix: Don't route to leader for single-use transactions in Client#execute_query #201
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This change makes it so queries against single-use transactions do not route to the leader, even when leader-aware routing is enabled, as these single-use transactions are read-only transactions with specific staleness requirements.
aandreassa
approved these changes
Nov 6, 2025
viacheslav-rostovtsev
deleted the
michaelherold/do-not-query-leader-with-read-only-txn
branch
3 tasks
Contributor
|
Thanks again! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This change makes it so queries against single-use transactions do not route to the leader, even when leader-aware routing is enabled, as these single-use transactions are read-only transactions with specific staleness requirements.
follows up on: #199
closes: #196