[
https://issues.apache.org/jira/browse/HADOOP-12548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15145465#comment-15145465
]
Larry McCay commented on HADOOP-12548:
--------------------------------------
I see...
So, when you say munged, you mean mistyped.
The mistyping of a filename isn't really as easily determined. It could be your
intention to check for an optionally available keystore at that location and
name. The fact that it returns null from getPassword is indicating that no
password was found by the valid jceks provider in the HDFS filesystem location
that you specified. That is the intended behavior.
I could be convinced that this is misleading. [~mattpaduano] - can you tell me
whether there was any logging that indicated the password couldn't be found in
the specified location? Perhaps a bit of better diagnostic logging would help
if there wasn't.
> 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)
