[
https://issues.apache.org/jira/browse/HADOOP-14738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16127599#comment-16127599
]
Aaron Fabbri commented on HADOOP-14738:
---------------------------------------
I'm happy to put up a patch for this once we have consensus.
{quote}
I could see an argument for removal without a deprecation cycle if S3N is a
high maintenance burden, we have high confidence that no one uses it, and the
same data remains accessible via S3A.
{quote}
I think #1 and #3 are true, but don't have confidence that no one uses it.
> Deprecate S3N in hadoop 3.0/2,9, target removal in Hadoop 3.1
> -------------------------------------------------------------
>
> Key: HADOOP-14738
> URL: https://issues.apache.org/jira/browse/HADOOP-14738
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: 2.9.0, 3.0.0-beta1
> Reporter: Steve Loughran
> Priority: Blocker
>
> We are all happy with S3A; it's been stable since Hadoop 2.7 and high-perf
> since Hadoop 2.8
> It's now time to kill S3N off, remove the source, the tests, the transitive
> dependencies.
> I propose that in Hadoop 3.0 beta we tell people off from using it, and link
> to a doc page (wiki?) about how to migrate (Change URLs, update config ops).
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
