[
https://issues.apache.org/jira/browse/HADOOP-12548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15145537#comment-15145537
]
Matthew Paduano commented on HADOOP-12548:
------------------------------------------
I don't see anything in the log.
I think this may be happening in AbstractJavaKeyStoreProvider
{code}
if (keystoreExists()) {
stashOriginalFilePermissions();
try (InputStream in = getInputStreamForFile()) {
keyStore.load(in, password);
}
} else {
createPermissions("700");
// required to create an empty keystore. *sigh*
keyStore.load(null, password);
}
{code}
and from JavaKeyStoreProvider
{code}
protected boolean keystoreExists() throws IOException {
return fs.exists(getPath());
}
protected InputStream getInputStreamForFile() throws IOException {
return fs.open(getPath());
}
{code}
If the fs.open() were simply attempted without the fs.exists() a
FileNotFoundException should be thrown.
But if other code relies on that alternate behavior, then I suppose all that
might be done is to add a log message?
> 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)
