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.
- 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.