[
https://issues.apache.org/jira/browse/HADOOP-12548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15144931#comment-15144931
]
Matthew Paduano commented on HADOOP-12548:
------------------------------------------
I want to clarify my comment. Upon more careful debugging, certain typos are
caught and messaged appropriately. The initial typo I tried did not. It
depends on where in the URL one happens to munge the string. The issue does
not seem to be related to the code in this patch.
I am using a test command with an option:
-Dhadoop.security.credential.provider.path=*jceks*://*hdfs*@localhost:9000*/user/mattp/aws.jceks*
there are (at least) three possible places one might mistype. An error in the
protocol or the filesystem scheme will be caught/notified appropriately. But
an error in the HDFS filename itself (the last portion of the above string)
does not. I did not track it down, but it may be a feature/bug in the conf
processing code(?).
> 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)
