Skip to content

branch-3.1: [fix](S3)Downgrade the AWS SDK version to avoid impacting other S3-compatible services. #58566 #58607

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.

Sign up for GitHub

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

Jump to bottom
Merged
morrySnow merged 1 commit into from
Dec 4, 2025
Merged

branch-3.1: [fix](S3)Downgrade the AWS SDK version to avoid impacting other S3-compatible services. #58566 #58607

morrySnow merged 1 commit into from
Dec 4, 2025

Conversation

@github-actions
Copy link
Contributor

@github-actions github-actions bot commented Dec 2, 2025

Cherry-picked from #58566

@CalvinKirs
[fix](S3)Downgrade the AWS SDK version to avoid impacting other S3-co…
0fc8db7 
…mpatible services. (#58566)

…

This PR addresses an issue related to AWS SDK for Java v2 S3 client
behavior described in:
aws/aws-sdk-java-v2#5805

Starting from newer versions of the SDK, the S3 client introduces
unexpected behavior that causes our application to fail during normal S3
operations. Due to this problem, we were forced to downgrade aws-s3 from
the latest version to 2.29.x, which restored correct functionality. The
regression affects stability in our production environment and prevents
us from upgrading the SDK.

#57226
@github-actions github-actions bot requested a review from morrySnow as a code owner December 2, 2025 04:57
@Thearas
Copy link
Contributor

Thearas commented Dec 2, 2025

Thank you for your contribution to Apache Doris.
Don't know what should be done next? See How to process your PR.

Please clearly describe your PR:

  1. What problem was fixed (it's best to include specific error reporting information). How it was fixed.
  2. Which behaviors were modified. What was the previous behavior, what is it now, why was it modified, and what possible impacts might there be.
  3. What features were added. Why was this function added?
  4. Which code was refactored and why was this part of the code refactored?
  5. Which functions were optimized and what is the difference before and after the optimization?

@dataroaring dataroaring closed this Dec 2, 2025
@dataroaring dataroaring reopened this Dec 2, 2025
@Thearas
Copy link
Contributor

Thearas commented Dec 2, 2025

run buildall

@hello-stephen
Copy link
Contributor

hello-stephen commented Dec 2, 2025

FE UT Coverage Report

Increment line coverage `` 🎉
Increment coverage report
Complete coverage report

@morrySnow morrySnow merged commit f51544b into branch-3.1 Dec 4, 2025
23 checks passed
@morrySnow morrySnow deleted the auto-pick-58566-branch-3.1 branch December 4, 2025 02:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@morrySnow morrySnow morrySnow approved these changes

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

6 participants

@Thearas @hello-stephen @morrySnow @dataroaring @CalvinKirs