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

QLDB Commit Transaction #176

Open
VigneshwaranSenthilvel opened this issue Feb 14, 2024 · 2 comments
Open

QLDB Commit Transaction #176

VigneshwaranSenthilvel opened this issue Feb 14, 2024 · 2 comments

Comments

@VigneshwaranSenthilvel
Copy link

Following the steps I followed but was not able to commit the qldb transaction using send comment function.

  • Started the session
  • Created the transaction
  • Execute the statement
  • Get the digest
  • Commit the transaction

Until committed things working fine. when committing the transaction using digest and transaction ID. getting errors always like digest not match

@onno-vos-dev
Copy link
Member

Hi @VigneshwaranSenthilvel Any chance you can provide any more information?

Quick google leads me to: aws/aws-sdk-go#3246 which seems to indicate an issue with the digest calculation... It seems to indicate that get_digest is insufficient to get the correct digest for executing the statement. I'll try to do some additional reading on this topic tonight but any additional information you could provide would help me, (hopefully) help you 👍 (Just ensure no sensitive data pls 😄)

@VigneshwaranSenthilvel
Copy link
Author

Hey @onno-vos-dev,

  • After examining the Go SDK on GitHub and going through the documentation, I found instructions regarding the encryption of statement and transaction IDs.
  • Before initiating a transaction, it's recommended to fetch the latest digest. After executing the transaction, another digest might be generated.

Despite following these steps, I haven't had success yet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants