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] [Updated] (HADOOP-14738) Deprecate S3N in hadoop 3.0/2,9, target removal in Hadoop 3.1
Date Mon, 04 Sep 2017 18:30:01 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-14738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Steve Loughran updated HADOOP-14738:
    Attachment: HADOOP-14739-001.patch

Patch 001

# tags everyhting as @ deprecated
# logs a warning on the first instance inited in a VM
# Implement {{createNonRecursive}} so that {{ITestS3NContractCreate}} works again.
# removed jets3t as an exported depencency of hadoop-aws
# moved all docs over to an s3n.md file
# provide instructions on migrating
# main docs are s3a only now, so clean up text, titles, anchors
# review docs, add anchors, promote headings
# move all troubleshooting into troubleshooting.md
# Qualify consistency warkings with more refs to using s3guard
# Add a few external links (EMR fs docs, HDP on distcp to s3, which is something I co-authored
a while back. We could copy that in directly, but copy-and-paste docs is as much a maintenance
issue as code copy and paste.

See [github|https://github.com/steveloughran/hadoop/tree/s3/HADOOP-14738-s3n-deprecate/hadoop-tools/hadoop-aws/src/site/markdown/tools/hadoop-aws]
for the MD to be rendered.

The jets3t export is something to debate It's a half-way migrate: you can still use s3n, you
just need to sort out the classpath. And it keeps the maven builds downstream much cleaner.

Tested against s3 ireland. I even found the regression in {{ITestS3NContractCreate}} which
we'd not picked up before (I fixed, rather than skip the tests because the fix was a simple
copy & paste from S3a)

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

View raw message