[ https://issues.apache.org/jira/browse/HADOOP-16505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16907281#comment-16907281 ]
Gabor Bota commented on HADOOP-16505: ------------------------------------- Thanks for working on this [~viczsaurav], and [~jojochuang] to notifying us! I think that the PR must be the current, because there is at least one test for this included in that. [~viczsaurav], could you include an integration test for this change? Also please run all integration test against an aws endpoint with these parameters at least: {{mvn clean verify -Dparallel-tests -DtestsThreadCount=8 -Ds3guard -Ddynamo}}, and tell us if it was successful. It would nice to show that the tests won't fail with the signer changed. > Add ability to register custom signer with AWS SignerFactory > ------------------------------------------------------------ > > 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 > Assignee: Saurav Verma > Priority: Major > Attachments: HADOOP-16505.patch, hadoop-16505-1.patch > > > 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: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org