[
https://issues.apache.org/jira/browse/HADOOP-16505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Saurav Verma updated HADOOP-16505:
----------------------------------
Description:
Currently, the AWS SignerFactory restricts the class of Signer algorithms that
can be used.
We require an ability to register a custom Signer. The SignerFactory supports
this functionality through its {{registerSigner}} method.
By providing a fully qualified classname to the existing parameter
{{fs.s3a.signing-algorithm}}, the custom signer can be registered.
was:
Currently, value of {{fs.s3a.signing-algorithm}} must be from the predefined
list of signer class in AWS SignerFactory.
This would enable users to register and use custom `Signature algorithm` for
aws s3a filesystem, passing it as value for {{fs.s3a.signing-algorithm}} in
configuration.
> Use custom signature algorithm for `fs.s3a.signing-algorithm`
> -------------------------------------------------------------
>
> Key: HADOOP-16505
> URL: https://issues.apache.org/jira/browse/HADOOP-16505
> Project: Hadoop Common
> Issue Type: Improvement
> Components: fs/s3, hadoop-aws
> Affects Versions: 3.3.0
> Reporter: Saurav Verma
> Priority: Major
>
> Currently, the AWS SignerFactory restricts the class of Signer algorithms
> that can be used.
> We require an ability to register a custom Signer. The SignerFactory supports
> this functionality through its {{registerSigner}} method.
> By providing a fully qualified classname to the existing parameter
> {{fs.s3a.signing-algorithm}}, the custom signer can be registered.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
