-
Notifications
You must be signed in to change notification settings - Fork 586
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(source): make s3 source compatible with minio #16521
Conversation
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 for the fix. Shall we add minio-targeted tests in CI?
I don’t think it’s necessary at first, because we already have s3, and adding another one will only make the CI heavier😄. |
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
@@ -58,8 +58,6 @@ impl<Src: OpendalSource> OpendalEnumerator<Src> { | |||
); | |||
} | |||
|
|||
builder.enable_virtual_host_style(); |
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.
cherry-pick it into release-1.9 because some users using the S3 bucket name with dot .
and will meet error here https://github.com/apache/opendal/blame/ac694375da955ea6d3461aee0bfafd5a5d774541/core/src/services/s3/backend.rs#L600-L614
I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?
This PR
enable_virtual_host_style
so that bothvirtual_path_style: s3.endpoint_url = 'http://127.0.0.1:9301'
andforce_path_style: s3.endpoint_url = 'http://<bucket>.127.0.0.1:9301'
can work well with minio. (Before this pr neither method works for minio. )backon
, refer to fix: fixwith_factor
assert Xuanwo/backon#68Checklist
./risedev check
(or alias,./risedev c
)Documentation
Release note
If this PR includes changes that directly affect users or other significant modifications relevant to the community, kindly draft a release note to provide a concise summary of these changes. Please prioritize highlighting the impact these changes will have on users.