Details
-
Sub-task
-
Status: Resolved
-
Blocker
-
Resolution: Fixed
-
2.9.0, 3.0.0-beta1
-
None
-
Incompatible change
-
Description
We are all happy with S3A; it's been stable since Hadoop 2.7 and high-perf since Hadoop 2.8
It's now time to kill S3N off, remove the source, the tests, the transitive dependencies. This patch does that.
It also removes the obsolete, original s3a output stream; the fast/block upload stream has been stable and is much more manageable and maintained (put differently: we don't ever look at the original S3A output stream, and tell people not to use it for performance reasons).
As well as cutting the features, this patch updates the aws docs with
- split out s3n migration page
- split out troubleshooting page
- rework of the "uploading data with s3a" section of index.md, as there's no need to discuss the slow upload except in the past tense...all that is needed is to list the buffering and thread tuning options of the block uploader.
Attachments
Attachments
Issue Links
- contains
-
HADOOP-13894 s3a troubleshooting to cover the "JSON parse error" message
- Resolved
-
HADOOP-14545 Uninitialized S3A instance NPEs on toString()
- Resolved
-
HADOOP-14834 Remove original S3A output stream
- Resolved
- duplicates
-
HADOOP-14746 Cut S3AOutputStream
- Resolved
- incorporates
-
HADOOP-14826 review S3 docs prior to 3.0-beta-1
- Resolved
- is duplicated by
-
HADOOP-14529 retire s3n
- Resolved
- supercedes
-
HADOOP-12981 Remove/deprecate s3native properties from S3NativeFileSystemConfigKeys and core-default.xml
- Resolved