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

Support for AWS Java SDK v2 #5

Closed
janario opened this issue Jan 8, 2019 · 7 comments · Fixed by #98
Closed

Support for AWS Java SDK v2 #5

janario opened this issue Jan 8, 2019 · 7 comments · Fixed by #98
Labels
enhancement New feature or request

Comments

@janario
Copy link

janario commented Jan 8, 2019

AWS Java SDK v2 was launched last year https://aws.amazon.com/blogs/developer/aws-sdk-for-java-2-x-released/

It would be nice to have this caching classes with the new API

@StevenEmelander StevenEmelander added the enhancement New feature or request label Jan 8, 2019
@StevenEmelander
Copy link

Thank you for reaching out with this request. The AWS Java SDK v2 was released in November and we have not yet investigated this. Incorporating AWS Java SDK v2 will be considered for a future release.

@sullis
Copy link

sullis commented Jan 11, 2019

see: #6

@oridool
Copy link

oridool commented Nov 2, 2020

see more recent SDK #13 with 2.15.19

This was linked to pull requests May 20, 2022
@simonmarty
Copy link
Contributor

We reviewed your request and in-order to prioritize it, we would like to understand your use-case to use SDKv2 over SDKv1. The two versions of the AWS SDK for Java can work together side-by-side without issue.

@simonmarty simonmarty closed this as not planned Won't fix, can't repro, duplicate, stale Jun 30, 2022
@oridool
Copy link

oridool commented Jun 30, 2022

@simonmarty ,
The use case is running the application on EKS and utilizing 'IAM Role for Service Account' (IRSA).
Unfortunately, SDK 1.x couldn't support IRSA at the time this issue was created.
According to this this , SDK 1.x added such support on Jan 2020.
I didn't try it, since I'm already using SDK 2.x using a fork of this project.
Still, I believe it would be better to upgrade to v2.x because it is more advanced and many people already using it and now they are limited.
Or - if the library can somehow support both versions, it would be great.

@maciejwalkowiak
Copy link

@simonmarty they can work side by side but that's good as a temporary workaround not as a final solution. Why would I want to have 2 versions of the same library in my classpath?

@renatomariscal
Copy link

we would like to understand your use-case to use SDKv2 over SDKv1.

This is unsatisfactory reason to dismiss this feature request. SDKv2 exists to replace v1. As such, tools like this one should be supporting, and promoting V2 usage. Not challenging its value like this answer.

@simonmarty simonmarty reopened this Aug 16, 2023
@simonmarty simonmarty mentioned this issue Aug 15, 2023
Merged
simonmarty added a commit that referenced this issue Aug 17, 2023
Closes #5 

*Description of changes:*

Provide a major version 2 version of the Java Caching Library.

Version 2 uses the Java SDK v2 under the hood. The library should be a
drop-in replacement, unless you currently provide a v1 client to the
caching library at creation. In that case, you will have to start
passing a v2 client instead.

Version 1 and version 2 will be maintained side by side in separate
branches.

By submitting this pull request, I confirm that my contribution is made
under the terms of the Apache 2.0 license.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
7 participants