hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mingliang Liu (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-12709) Deprecate s3:// in branch-2,; cut from trunk
Date Thu, 02 Jun 2016 21:21:59 GMT

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

Mingliang Liu updated HADOOP-12709:
    Attachment: HADOOP-12709.005.patch

Rebase from {{trunk}}.

> 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, HADOOP-12709.001.patch, HADOOP-12709.002.patch,
HADOOP-12709.003.patch, HADOOP-12709.004.patch, HADOOP-12709.005.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

To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org

View raw message