[
https://issues.apache.org/jira/browse/HADOOP-12709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mingliang Liu updated HADOOP-12709:
-----------------------------------
Description:
UPDATE: This JIRA ticket is to track the effort of cutting the s3:// from
{{trunk}} branch. Please see the cloned JIRA ticket [HADOOP-13239] for
deprecating s3:// from {{branch-2}}.
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.
was:
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.
> Cut s3:// 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: 3.0.0-alpha1
> 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
>
>
> UPDATE: This JIRA ticket is to track the effort of cutting the s3:// from
> {{trunk}} branch. Please see the cloned JIRA ticket [HADOOP-13239] for
> deprecating s3:// from {{branch-2}}.
> 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)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
