Skip to content

not compatible with java sdk2 #35

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

Closed
jkuehl2 opened this issue Apr 15, 2019 · 5 comments
Closed

not compatible with java sdk2 #35

jkuehl2 opened this issue Apr 15, 2019 · 5 comments

Comments

@jkuehl2
Copy link

jkuehl2 commented Apr 15, 2019

Is it planned to migrate to aws java sdk2?

@robin-aws
Copy link

Hi @jkuehl2! We are definitely planning to migrate this library and the other supported SQS libraries to v2 of the Java SDK, but we do not yet have an ETA. v2 changes quite a bit so it will not be entirely trivial.

@AlexBroadbent
Copy link

Any update on this? I am trying to upgrade from v1 to v2 but am blocked on this library.

@robin-aws
Copy link

robin-aws commented Aug 1, 2019

Hi Alex! This is still high on our backlog, and I recently scoped out the v1 to v2 interface changes to estimate how much work it will be (for this library as well as the other custom SQS clients). As expected it's not trivial since all the interfaces changed quite a bit. I'll add your +1 for this library internally and push for getting the resources assigned.

@kito99
Copy link

kito99 commented May 11, 2020

@robin-aws any updates? I wonder if we should just manually put the data in an S3 bucket and have a reference to it in our message

@jimhooker2002
Copy link

Piling on here :-) one more person blocked here, we really want to get onto SDK V2, but this blocks us doing that.

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

6 participants