You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Version Information
SDK: v0.23.1-0.20200714212036-c1ad81608c5c
Go: 1.14
Is your feature request related to a problem? Please describe.
It is difficult to disambiguate Transaction cancellation reasons. There's a similar issue in the AWS SDK v1, which appears to have been fixed in the v1.28 release but not mirrored to v2.
Describe the solution you'd like
I'd like to be able to unwrap the error from a transaction request to obtain the underlying reason for failure per-item in the transaction. It'd be great if there were a strongly typed approach to this.
I think the solution in the V1 SDK makes sense, so I'm really just hoping for a port of that functionality.
Describe alternatives you've considered
The JS SDK has a similar issue. The current suggestion there is to use string parsing, which is what we're currently doing in our project to handle this.
The text was updated successfully, but these errors were encountered:
The latest version (+ v0.25.0) of the v2 preview SDK now generates typed errors for all APIs. This includes the DynamoDB's Cancellation reasons in TransactionCanceledException error response.
Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.
Version Information
SDK: v0.23.1-0.20200714212036-c1ad81608c5c
Go: 1.14
Is your feature request related to a problem? Please describe.
It is difficult to disambiguate Transaction cancellation reasons. There's a similar issue in the AWS SDK v1, which appears to have been fixed in the v1.28 release but not mirrored to v2.
Describe the solution you'd like
I'd like to be able to unwrap the error from a transaction request to obtain the underlying reason for failure per-item in the transaction. It'd be great if there were a strongly typed approach to this.
I think the solution in the V1 SDK makes sense, so I'm really just hoping for a port of that functionality.
Describe alternatives you've considered
The JS SDK has a similar issue. The current suggestion there is to use string parsing, which is what we're currently doing in our project to handle this.
The text was updated successfully, but these errors were encountered: