-
Notifications
You must be signed in to change notification settings - Fork 50
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
aws-sdk-go-v2 support #2
Comments
Thanks for the feedback. Supporting the AWS SDK for Go v2 is definitely on our radar, but we do not have a timeline to share at this time. |
hi is anyone working on v2 ? |
Unfortunately, AWS Go SDK v2 is currently not on our roadmap since it's still in developer preview stage. Once it's generally available, we will start our plan to support v2. |
Sounds like this is getting pretty close: |
AWS SDK v2 for Go was GA'd on 2021-01-19 per https://aws.amazon.com/blogs/developer/aws-sdk-for-go-version-2-general-availability Can we get an update on this? |
Hi all, I've forked the project and created a compatibility layer for go sdk v2. You can check it out here. I've currently only written support for If you want to try it out all you need to do is add a replace line in your
If there's interest in supporting the other API calls let me know. I'm pretty sure that updating the project to support Enjoy! |
Any update on support for AWS Go SDK v2 ? We have been using the new version of SDK for a while & we wanted to move to DAX in order to improve the overall response times but it requires us to downgrade back to SDK v1 thereby loosing all benefits of SDK v2 & requiring additional effort of migration. |
A friendly follow-up to the question and request above. It is quite cumbersome to be maintaining sets of two different libraries depending on whether we are accessing DynamoDB directly (using SDK v2) or via DAX cache (using SDK v1) - it would help us a lot if DAX client was updated to fully support AWS SDK v2 which has been released almost a year ago. Thank you in advance for your help or at least an indication of when (if ever) we might expect this library to support SDK v2. |
Same question here about support. Now that the aws go sdk has an official release, when can we expect to get support in this library? |
I have the same question as we developed everything using the V2 SDK and we wouldn't want to go back to V1 just for DAX 👍 |
Any update on this? had to go back to v1 just for DAX. |
same here. Everything is on V2 and we need to use V1 just for DAX. Please plan for it! |
@mt0321, any chance you or your team could include this in your timeline? |
@sumitsa-amazon is there any plans to support this? I'd love to use DAX, but going back to v1 for it is not in the cards. |
+1 |
4 similar comments
+1 |
+1 |
+1 |
+1 |
+1 Is #43 enough to upgrade to v2? |
+1 |
Still no updates on supporting this? Its been open for more than five years. We've already gone through the painful process of migrating to the v2 SDK and are not keen at all to migrate back to v1 just to use DAX. |
💀 |
Are there any plans to release a version of this client that support
aws-sdk-go-v2
? At present it requires plain oldaws-sdk-go
We had work simultaneously underway to upgrade our go libs to v2 and to support DAX and now we have conflicting PRs. Obviously we'll have to put the v2 upgrade on hold to support DAX for now, I'm just wondering if there's a timeframe, or if it's even on the radar.
The text was updated successfully, but these errors were encountered: