-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
[Enhancement] to avoid s3://
not supported case
#42369
Conversation
@@ -0,0 +1,6 @@ | |||
<configuration> | |||
<property> | |||
<name>fs.s3.impl</name> |
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.
mapping s3a
also
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.
no need to map s3a, s3a is already builtin mapped.
https://hadoop.apache.org/docs/current/hadoop-aws/tools/hadoop-aws/index.html
Signed-off-by: yanz <[email protected]>
75e404f
to
8bc0be1
Compare
Signed-off-by: yanz <[email protected]>
Quality Gate passedIssues Measures |
[FE Incremental Coverage Report]✅ pass : 0 / 0 (0%) |
[BE Incremental Coverage Report]✅ pass : 0 / 0 (0%) |
@Mergifyio backport branch-3.2 |
@Mergifyio backport branch-3.1 |
@Mergifyio backport branch-3.0 |
@Mergifyio backport branch-2.5 |
✅ Backports have been created
|
✅ Backports have been created
|
✅ Backports have been created
|
✅ Backports have been created
|
Signed-off-by: yanz <[email protected]> (cherry picked from commit 8956689)
Signed-off-by: yanz <[email protected]> (cherry picked from commit 8956689) # Conflicts: # be/CMakeLists.txt # build.sh
Signed-off-by: yanz <[email protected]> (cherry picked from commit 8956689) # Conflicts: # be/CMakeLists.txt
Signed-off-by: yanz <[email protected]> (cherry picked from commit 8956689) # Conflicts: # be/CMakeLists.txt # build.sh
…42457) Co-authored-by: dirtysalt <[email protected]>
…42458) Signed-off-by: yanz <[email protected]> Co-authored-by: dirtysalt <[email protected]>
…42459) Signed-off-by: yanz <[email protected]> Co-authored-by: dirtysalt <[email protected]>
…42460) Signed-off-by: yanz <[email protected]> Co-authored-by: dirtysalt <[email protected]>
Why I'm doing:
Some user create database s3 glue catalog reports
Some user hit same problem when access HURI MOR table
What I'm doing:
I think we can make s3 scheme maps to
org.apache.hadoop.fs.s3a.S3AFileSystem
by default.Fixes #issue
What type of PR is this:
Does this PR entail a change in behavior?
If yes, please specify the type of change:
Checklist:
Bugfix cherry-pick branch check: