hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-14738) Deprecate S3N in hadoop 3.0/2,9, target removal in Hadoop 3.1
Date Tue, 15 Aug 2017 10:17:02 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-14738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16127039#comment-16127039
] 

Steve Loughran commented on HADOOP-14738:
-----------------------------------------

depends what we think is needed. I'm thinking of: rm docs, test, existing code. Add new section
"migrating to s3a" (wiki?) and have the s3n FS impl print this to tell people what to do.


We can't do an automated migration as the key settings are all different

> 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-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org


Mime
View raw message