IGNITE-27117 Don't abort execution of previous statements when an error occurs in a multi-statement query #7099
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
xtern
changed the title
xtern
changed the title
…t preceding statements
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
https://issues.apache.org/jira/browse/IGNITE-27117
The new JDBC driver executes Statement.executeBatch() as a single multi-statement query and counts the number of updates. The problem occurs if one of the statements contains an error, in which case all statements are canceled and as a result the driver may incorrectly count the number of updates.
It is proposed not to cancel all at once.
See changes in
MultiStatementHandler.cancelAll()andScriptTransactionWrapperImpl.finalise(Throwable),