-
Notifications
You must be signed in to change notification settings - Fork 3.8k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
108447: server: support separate transactions on sql api r=THardy98 a=THardy98 Part of: #102386 This change introduces a `separate_txns` field to the sql api endpoint. This field allows callers to run provided statements in separate transactions. Failures in separate transactions are scoped to their respective transaction and do not interfere with the execution of subsequent transactions. The exception to this case is if the max response size is exceeded. If the response size is exceeded in an earlier transaction, it will still exceed the limit in subsequent transactions. The response-level error using `separate_txns` is a generic message: `separate transaction payload encountered transaction error(s)`, indicating that an error has occurred in at least one of the transactions. We additionally add a `stop_on_error` field to allow callers to stop execution of subsequent txns (i.e. in the case where `separate_txns` is true). Release note: None Co-authored-by: Thomas Hardy <[email protected]>
- Loading branch information
Showing
4 changed files
with
466 additions
and
17 deletions.
There are no files selected for viewing
This file contains 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 file contains 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 file contains 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
Oops, something went wrong.