You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Siddharth Seth (JIRA)" <ji...@apache.org> on 2019/07/23 07:59:00 UTC
[jira] [Updated] (HADOOP-16449) Allow an empty credential provider
chain, separate chains for S3 and DDB
[ https://issues.apache.org/jira/browse/HADOOP-16449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Siddharth Seth updated HADOOP-16449:
------------------------------------
Attachment: HADOOP-16449.01.patch
> 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
> 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: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org