[
https://issues.apache.org/jira/browse/HADOOP-18747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17747555#comment-17747555
]
Ahmar Suhail commented on HADOOP-18747:
---------------------------------------
* Yeah, the NPE isn't ideal, we could update with something like throw new
IllegalArgumentException("unknown signer type, ensure it's included using
fs.s3a.custom.signers" );
* The CRT doesn't currently support custom signers, which is why we don't use
it yet. We may want to add it in the future (but without custom signer support,
it will have to be an optional client and not the default)
* The async client supports custom signers, and they are configured in the
code, same as the sync client. in AwsClientConfig.createClientConfigBuilder
> AWS SDK V2 - sigv2 support
> --------------------------
>
> Key: HADOOP-18747
> URL: https://issues.apache.org/jira/browse/HADOOP-18747
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: 3.4.0
> Reporter: Ahmar Suhail
> Priority: Major
>
> AWS SDK V2 does not support sigV2 signing. However, the S3 client supports
> configurable signers so a custom sigV2 signer can be implemented and
> configured.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
