Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Duplicate
-
3.0.0-alpha3
-
None
-
None
Description
S3A is now stable and performant, s3n is unmaintained.
Moving from s3n to s3a is straightforward: change your key names.
I propose
- remove s3n main and test source, except for a reference in the docs, "gone"
- drop the jets3t JAR
- migrate any open s3n JIRAs which apply to s3a too over to being about s3a
- close any other remaining s3n JIRAs
short term, branch-2 and 3.0 alpha should issue a deprecation warning the first time s3n is used in a JVM
Attachments
Issue Links
- duplicates
-
HADOOP-14738 Remove S3N and obsolete bits of S3A; rework docs
-
- Resolved
-