This repository was archived by the owner on Apr 7, 2026. It is now read-only.
feat: add option for cancelling queries when closing client#3276
Merged
feat: add option for cancelling queries when closing client#3276
Conversation
Adds an option to keep track of all running queries and cancel these when the client is closed.
rahul2393
approved these changes
Aug 21, 2024
lqiu96
pushed a commit
that referenced
this pull request
Sep 10, 2024
* feat: add option for cancelling queries when closing client Adds an option to keep track of all running queries and cancel these when the client is closed. * test: unflake test cases * fix: cancel query by default for batch transactions * chore: cleanup
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Adds the possibility to keep track of all running queries and cancel these when the client is closed. This option is currently only used for queries that are started by
BatchReadOnlyTransactions, as these do not use pooled sessions. Queries that use pooled sessions are automatically cancelled when the client is closed, because the sessions are deleted.