Description
Apparently some third party S3-API object stores have empty etags for multipart uploads.
We don't have any tests to explore this (just small file uploads).
Proposed
*set fs.s3a.etag.checksum.enabled" before huge file, MPU and committer tests
- warn (fail?) if nothing comes back.
If true, it means that the store isn't going to be detect changes to a large file during copy/read
Attachments
Issue Links
- relates to
-
HADOOP-15625 S3A input stream to use etags/version number to detect changed source files
- Resolved
-
HADOOP-16085 S3Guard: use object version or etags to protect against inconsistent read after replace/overwrite
- Resolved