Expose transaction cancellation reasons #1144
Merged
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 will allow the caller to know e.g. which of the transaction items ran into a conflict, which can sometimes allow app logic to better handle the error without needing to make more requests.
A transaction cancellation response has the following shape:
{ "__type": "com.amazonaws.dynamodb.v20120810#TransactionCanceledException", "CancellationReasons": [ { "Code": "None" }, { "Code": "ConditionalCheckFailed", "Message": "The conditional request failed" } ], "Message": "Transaction cancelled, please refer cancellation reasons for specific reasons [None, ConditionalCheckFailed]" }where the first item was not a reason for cancellation and the second one was.
Curiously, this field is not parsed by botocore: only some of the AWS SDKs (Java, Ruby...) parse it.