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

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

Good Q.

On one hand: we've not given any warning

On the other: we have a full replacement, so migration is all you need to do. 
It's not like we cut S3N out.

In that case we could go
# branch-2, 2.8 -> warn 
# trunk -> add that wrapper class which tells off user, maybe links to wiki 
entry on how to migrate. Given changes in management of auth details (which is 
much more than just changed key names), I'd not want to rush to copying over 
the old secret names, instead help people move

> 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
>
> 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

Reply via email to