You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-issues@hadoop.apache.org by "Steve Loughran (JIRA)" <ji...@apache.org> on 2016/01/14 19:56:40 UTC

[jira] [Created] (HADOOP-12709) Deprecate s3:// in branch-2,; cut from trunk

Steve Loughran created HADOOP-12709:
---------------------------------------

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


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
(v6.3.4#6332)