-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
[Document] Remove a fs.oss.credentials.provider
option
#7507
Conversation
fs.oss.credentials.provider
option caused by a NoSuchMethodExceptionfs.oss.credentials.provider
option
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.
Yes. We did clean in #7332 . But seem like not cleaned up. Thanks @loustler ! cc @Carl-Zhou-CN
@loustler Could you please help me globally search for 'org.apache.hadoop.fs.aliyun.oss.AliyunCredentialsProvider' and completely remove this configuration? Thank you very much for your help. |
@Carl-Zhou-CN A I found those by IntelliJ. Should I change this?
|
I think it can be removed from the test case, @Hisoka-X what do you think? |
yes. |
@Carl-Zhou-CN @Hisoka-X |
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
* Remove a `fs.oss.credentials.provider` option caused by a NoSuchMethodException * Add RELEASE NOTE * Remove a `fs.oss.credentials.provider` option from test codes * fix --------- Co-authored-by: Dongyeon <[email protected]>
* Remove a `fs.oss.credentials.provider` option caused by a NoSuchMethodException * Add RELEASE NOTE * Remove a `fs.oss.credentials.provider` option from test codes * fix --------- Co-authored-by: Dongyeon <[email protected]>
Purpose of this pull request
Remove a
fs.oss.credentials.provider
configuration from checkpoint with OSS storage. Because if it provided into a hadoop configuration, it trying to find a constructor has ofURL
andConfiguration
, and it throws a exception. Because aAliyunCredentialsProvider
class only have a single constructor which requires aConfiguration
class.It leads users like me to be confused/misunderstood, so we need to fix documents about it for users.
These are all release hadoop-aliyun source codes about load a credential provider
Hadoop 3.1.4
https://github.com/apache/hadoop/blob/1e877761e8dadd71effef30e592368f7fe66a61b/hadoop-tools/hadoop-aliyun/src/main/java/org/apache/hadoop/fs/aliyun/oss/AliyunOSSUtils.java#L105-L141
https://github.com/apache/hadoop/blob/1e877761e8dadd71effef30e592368f7fe66a61b/hadoop-tools/hadoop-aliyun/src/main/java/org/apache/hadoop/fs/aliyun/oss/AliyunCredentialsProvider.java#L35-L67
Hadoop 3.3.6
https://github.com/apache/hadoop/blob/1be78238728da9266a4f88195058f08fd012bf9c/hadoop-tools/hadoop-aliyun/src/main/java/org/apache/hadoop/fs/aliyun/oss/AliyunOSSUtils.java#L106-L143
https://github.com/apache/hadoop/blob/1be78238728da9266a4f88195058f08fd012bf9c/hadoop-tools/hadoop-aliyun/src/main/java/org/apache/hadoop/fs/aliyun/oss/AliyunCredentialsProvider.java#L35-L67
Error stacktrace
Does this PR introduce any user-facing change?
YES
seatunnel: engine: checkpoint: interval: 6000 timeout: 7000 storage: type: hdfs max-retained: 3 plugin-config: storage.type: oss oss.bucket: your-bucket fs.oss.accessKeyId: your-access-key fs.oss.accessKeySecret: your-secret-key fs.oss.endpoint: endpoint address - fs.oss.credentials.provider: org.apache.hadoop.fs.aliyun.oss.AliyunCredentialsProvider
How was this patch tested?
It tested with release 2.3.7 with OSS
Check list
New License Guide
release-note
.