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
[fix](backup) missing use_path_style properties for minio #25803
Conversation
run buildall |
clang-tidy review says "All clean, LGTM! 👍" |
TeamCity be ut coverage result: |
run external |
c413613
to
01fe86f
Compare
run buildall |
clang-tidy review says "All clean, LGTM! 👍" |
(From new machine)TeamCity pipeline, clickbench performance test result: |
01fe86f
to
b75bcbd
Compare
run buildall |
clang-tidy review says "All clean, LGTM! 👍" |
(From new machine)TeamCity pipeline, clickbench performance test result: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
PR approved by anyone and no changes requested. |
PR approved by at least one committer and no changes requested. |
Follow apache#25496. In apache#25496, I fixed the issue that the aws s3 properties are invalid when passing from FE to BE. But it missed the `use_path_style` property, which is useful for minio access. This PR fix it.
Follow apache#25496. In apache#25496, I fixed the issue that the aws s3 properties are invalid when passing from FE to BE. But it missed the `use_path_style` property, which is useful for minio access. This PR fix it.
Follow apache#25496. In apache#25496, I fixed the issue that the aws s3 properties are invalid when passing from FE to BE. But it missed the `use_path_style` property, which is useful for minio access. This PR fix it.
Proposed changes
Follow #25496.
In #25496, I fixed the issue that the aws s3 properties are invalid when passing from FE to BE.
But it missed the
use_path_style
property, which is useful for minio access.This PR fix it.
The test cases for minio will be added after this PR #25424 merged
Further comments
If this is a relatively large or complex change, kick off the discussion at dev@doris.apache.org by explaining why you chose the solution you did and what alternatives you considered, etc...