hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Nauroth (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-12709) Deprecate s3:// in branch-2,; cut from trunk
Date Fri, 26 Feb 2016 20:07:18 GMT

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

Chris Nauroth commented on HADOOP-12709:

I'm in favor of the proposal to remove s3 from trunk.  I haven't had time to review the patch
yet, but I'll put it in my queue.

> Deprecate s3:// in branch-2,; cut from trunk
> --------------------------------------------
>                 Key: HADOOP-12709
>                 URL: https://issues.apache.org/jira/browse/HADOOP-12709
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: fs/s3
>    Affects Versions: 2.8.0
>            Reporter: Steve Loughran
>            Assignee: Mingliang Liu
>         Attachments: HADOOP-12709.000.patch
> The fact that s3:// was broken in Hadoop 2.7 *and nobody noticed until now* shows that
it's not being used. while invaluable at the time, s3n and especially s3a render it obsolete
except for reading existing data.
> I propose
> # Mark Java source as {{@deprecated}}
> # Warn the first time in a JVM that an S3 instance is created, "deprecated -will be removed
in future releases"
> # in Hadoop trunk we really cut it. Maybe have an attic project (external?) which holds
it for anyone who still wants it. Or: retain the code but remove the {{fs.s3.impl}} config
option, so you have to explicitly add it for use.

This message was sent by Atlassian JIRA

View raw message