[
https://issues.apache.org/jira/browse/HADOOP-16449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16891923#comment-16891923
]
Steve Loughran commented on HADOOP-16449:
-----------------------------------------
I have comments, but first can you submit it as a github PR, and state which
s3a endpoint you ran against
Key point: DDB shouldn't contain any of the logic about how to get its auth
chain. Thats something which should come to it via the StoreContext used to
help bind it to the rest of the S3A connector.
> Allow an empty credential provider chain, separate chains for S3 and DDB
> ------------------------------------------------------------------------
>
> Key: HADOOP-16449
> URL: https://issues.apache.org/jira/browse/HADOOP-16449
> Project: Hadoop Common
> Issue Type: Improvement
> Components: fs/s3
> Affects Versions: 3.2.0
> Reporter: Siddharth Seth
> Assignee: Siddharth Seth
> Priority: Major
> Attachments: HADOOP-16449.01.patch
>
>
> Currently, credentials cannot be empty (falls back to using the default
> chain). Credentials for S3 and DDB are always the same.
> In some cases it can be useful to use a different credential chain for S3 and
> DDB, as well as allow for an empty credential chain.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
