[
https://issues.apache.org/jira/browse/HADOOP-18820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17755620#comment-17755620
]
ASF GitHub Bot commented on HADOOP-18820:
-----------------------------------------
steveloughran commented on PR #5872:
URL: https://github.com/apache/hadoop/pull/5872#issuecomment-1682609014
OK, I added the setConf() feature. Means thing is potentially useful.
V1 handlers get an error, as seen in the test
```
2023-08-17 17:24:42,849 [setup] WARN s3a.SDKV2Upgrade
(LogExactlyOnce.java:warn(39)) - Ignoring V1 SDK request handlers set in
fs.s3a.audit.request.handlers: not-valid-class
```
Note, AFAIK nobody has ever added a custom handler.
> AWS SDK v2: make the v1 bridging support optional
> -------------------------------------------------
>
> Key: HADOOP-18820
> URL: https://issues.apache.org/jira/browse/HADOOP-18820
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: 3.4.0
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Priority: Major
> Labels: pull-request-available
>
> The AWS SDK v2 code includes the v1 sdk core for plugin support of
> * existing credential providers
> * delegation token binding
> I propose we break #2 and rely on those who have implemented to to upgrade.
> apart from all the needless changes the v2 SDK did to the api (why?) this is
> fairly straighforward
> for #1: fix through reflection, retaining a v1 sdk dependency at test time so
> we can verify that the binder works.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
