Steve Loughran commented on HADOOP-14738:

Some ideas

* For those people who explicitly go {{fs.s3n.impl = 
org.apache.hadoop.fs.s3native.NativeS3FileSystem}}, we could retain an FS impl 
there which extended S3A and warned users off it
* Could we pick up the old key names (or at least fs.s3a equivalents) as 
deprecated values? I'm reluctant to do this, as {{Configuration.getPassword()}} 
doesn't handle deprecation.

> Deprecate S3N in hadoop 3.0, 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

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