[SPARK-47632][BUILD] Ban com.amazonaws:aws-java-sdk-bundle dependency
#45759
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dongjoon-hyun
commented
Mar 28, 2024
Member
Author
dongjoon-hyun
left a comment
dongjoon-hyun
left a comment
There was a problem hiding this comment.
Hi, @huaxingao .
Could you review this PR?
huaxingao
approved these changes
Mar 28, 2024
Contributor
huaxingao
left a comment
huaxingao
left a comment
There was a problem hiding this comment.
LGTM. Thanks for the PR @dongjoon-hyun
Member
Author
|
Thank you, @huaxingao ! |
Member
Author
|
Merged to master for Apache Spark 4.0.0. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this pull request?
This PR aims to ban
AWS SKD for Java v1. We migrated to v2 via the following.Why are the changes needed?
To ensure the migration to AWS SDK for Java v2 because of the following the end of support schedule.
v2is strongly recommended since July.Does this PR introduce any user-facing change?
No, this PR only prevents mixing this old dependency in the future.
How was this patch tested?
Pass the CIs.
Was this patch authored or co-authored using generative AI tooling?
No.