Description
I think it is time to remove the "experimental feature" designation in the site docs for S3Guard. Discuss.
Attachments
Issue Links
- depends upon
-
HADOOP-13936 S3Guard: DynamoDB can go out of sync with S3AFileSystem.delete()
- Resolved
-
HADOOP-15183 S3Guard store becomes inconsistent after partial failure of rename
- Resolved
-
HADOOP-14000 S3guard metadata stores to support millions of entries
- Resolved
-
HADOOP-14576 s3guard DynamoDB resource not found: tables not ACTIVE state after initial connection
- Resolved
-
HADOOP-15035 S3Guard to perform retry and translation of exceptions
- Resolved
-
HADOOP-15604 Bulk commits of S3A MPUs place needless excessive load on S3 & S3Guard
- Resolved
-
HADOOP-16085 S3Guard: use object version or etags to protect against inconsistent read after replace/overwrite
- Resolved
-
HADOOP-16118 S3Guard to support on-demand DDB tables
- Resolved
-
HADOOP-16184 S3Guard: Handle OOB deletions and creation of a file which has a tombstone marker
- Resolved
-
HADOOP-14759 S3GuardTool prune to prune specific bucket entries
- Resolved
-
HADOOP-13980 S3Guard CLI: Add fsck check and fix commands
- In Progress
- is blocked by
-
HADOOP-16380 S3A tombstones can confuse empty directory status
- Resolved
-
HADOOP-16207 Improved S3A MR tests
- Resolved
-
HADOOP-15999 S3Guard: Better support for out-of-band operations
- Resolved
-
HADOOP-16187 ITestS3GuardToolDynamoDB test failures
- Resolved
-
HADOOP-16490 Avoid/handle cached 404s during S3A file creation
- Resolved
-
HADOOP-16501 s3guard auth path checks only check against unqualified source path
- Resolved
-
HADOOP-16278 With S3A Filesystem, Long Running services End up Doing lot of GC and eventually die
- Resolved
- links to