[
https://issues.apache.org/jira/browse/HADOOP-16445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16912592#comment-16912592
]
Siddharth Seth commented on HADOOP-16445:
-----------------------------------------
Have posted a PR.
On the STS question - at the moment, it is going to end up using the existing
configuration parameter - i.e. fs.s3a.signing-algorithm - and the overrides for
S3A/DDB will not have an affect on this. I could add an override for STS as
well if that makes sense.
For STS - if fs.s3a.signing-algorithm is not set, the signer is not overridden.
For S3 - If fs.s3a.s3.signing-algorithm is set - the signer is overriden with
this value. Otherwise the existing behaviour continues (similar to what is
decsribed for STS above)
For DDB - If fs.s3a.ddb.signing-algorithm is set - the signer is overriden
with this value. Otherwise the existing behaviour continues (similar to what is
decsribed for STS above)
> Allow separate custom signing algorithms for S3 and DDB
> -------------------------------------------------------
>
> Key: HADOOP-16445
> URL: https://issues.apache.org/jira/browse/HADOOP-16445
> Project: Hadoop Common
> Issue Type: Improvement
> Components: fs/s3
> Reporter: Siddharth Seth
> Assignee: Siddharth Seth
> Priority: Major
> Attachments: HADOOP-16445.01.patch, HADOOP-16445.02.patch
>
>
> fs.s3a.signing-algorithm allows overriding the signer. This applies to both
> the S3 and DDB clients. Need to be able to specify separate signing algorithm
> overrides for S3 and DDB.
>
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
