Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[dynamoDB] Acquire Cancellation Reasons from a TransactionCanceledException #663

Closed
dallbee opened this issue Jul 26, 2020 · 3 comments
Closed
Labels
feature-request A feature should be added or improved.

Comments

@dallbee
Copy link

dallbee commented Jul 26, 2020

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.

@dallbee dallbee added the feature-request A feature should be added or improved. label Jul 26, 2020
@jasdel
Copy link
Contributor

jasdel commented Nov 11, 2020

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.

@jasdel jasdel closed this as completed Nov 11, 2020
@github-actions
Copy link

⚠️COMMENT VISIBILITY WARNING⚠️

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.

@proxy-hatch
Copy link

any example for this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request A feature should be added or improved.
Projects
None yet
Development

No branches or pull requests

3 participants