[
https://issues.apache.org/jira/browse/HADOOP-12548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15145959#comment-15145959
]
Thomas Demoor commented on HADOOP-12548:
----------------------------------------
Hi [~lmccay],
thanks, finally someone cleaned up our initialize() mess ;) Possibly, some
outstanding patches will no longer merge but that's a minor inconvenience, it
needed to be done.
# My take:
** Don't think s3 is still used, the 'inode-tricks' it tries to pull-off are
guaranteed data loss :P
** s3n is still used but is planned to be deprecated once s3a is considered
fully stable: [[email protected]] has been rejecting non-critical patches to
s3n and pointing those people to s3a for a while now (recent example:
HADOOP-12353). FYI Most work on stabilizing s3a is grouped in HADOOP-11694.
HADOOP-9565 is also relevant (2x write performance).
# Good idea. Now that your patch has secured the access credentials it makes
sense to do the same for the proxy password.
> 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)
