[
https://issues.apache.org/jira/browse/HADOOP-14738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16154466#comment-16154466
]
Andrew Wang commented on HADOOP-14738:
--------------------------------------
Hi Steve, thanks for the patch,
I'd rather we keep the jets3t scope at "compile" if we're going to keep it at
all. It punts the classpath problems to end users, who are less equipped to
deal with it. IMO features should be fully supported or not supported at all.
Removing in 3.0 also seems better than removing in 3.1 since at least 3.0 is a
major release.
Whether to remove or not depends on how often S3N is used, and how hard it is
to use S3A instead. I'll defer to subject matter experts like yourself and
Aaron on this question. If it's not used and easy to migrate, then I'm +1 on
removing in 3.0.
> Deprecate S3N in hadoop 3.0/2,9, target removal in Hadoop 3.1; rework docs
> --------------------------------------------------------------------------
>
> 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
> Assignee: Steve Loughran
> Priority: Blocker
> Attachments: HADOOP-14739-001.patch
>
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
