[
https://issues.apache.org/jira/browse/HADOOP-12548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15144924#comment-15144924
]
Chris Nauroth commented on HADOOP-12548:
----------------------------------------
[~mattpaduano], thank you for testing. Patch v007 does look like the kind of
thing I had in mind for letting the exceptions propagate during initialization,
so I'm also curious to see more details on any shortcomings you noticed in the
error messages.
Are you referring to this error from within the Amazon code?
http://grepcode.com/file/repo1.maven.org/maven2/com.amazonaws/aws-java-sdk/1.8.1/com/amazonaws/auth/AWSCredentialsProviderChain.java#112
I would have expected that with patch v007, a misconfiguration would be an
initialization error, so execution never would even reach the point of trying
to walk through the credential chain. Maybe I am missing something.
> read s3 creds from a Credential Provider
> ----------------------------------------
>
> Key: HADOOP-12548
> URL: https://issues.apache.org/jira/browse/HADOOP-12548
> Project: Hadoop Common
> Issue Type: New Feature
> Components: fs/s3
> Reporter: Allen Wittenauer
> Assignee: Larry McCay
> Attachments: CredentialProviderAPIforS3FS-002.pdf,
> HADOOP-12548-01.patch, HADOOP-12548-02.patch, HADOOP-12548-03.patch,
> HADOOP-12548-04.patch, HADOOP-12548-05.patch, HADOOP-12548-06.patch,
> HADOOP-12548-07.patch
>
>
> It would be good if we could read s3 creds from a source other than via a
> java property/Hadoop configuration option
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
