Details
-
Task
-
Status: Resolved
-
Major
-
Resolution: Implemented
-
None
Description
On uploading a file through s3g an ETag header should be provided:
- in the case of a single file/part upload it represents MD5 of the file content
- if the file will be uploaded using a multipart upload then the ETag of the object is computed as MD5 of all individual part checksums:
// e1 = MD5(part-1) // e2 = MD5(part-2) // ... // eN = MD5(part-N) // ETag = MD5(e1 || e2 || e3 ... || eN) || -N // For example: ceb8853ddc5086cc4ab9e149f8f09c88-5
Computed ETag should be stored as a key metadata
Attachments
Issue Links
- causes
-
HDDS-10587 Reset the thread-local MessageDigest instance during exception
- Resolved
- contains
-
HDDS-9115 Provide ETag in a response header on file downloading through s3g
- Resolved
- is a parent of
-
HDDS-10403 CopyObject should set ETag based on the key content
- Resolved
- is part of
-
HDDS-792 Use md5 hash as ETag for Ozone S3 objects
- Resolved
- is related to
-
HDDS-9680 Use md5 hash of multipart object part's content as ETag
- Resolved
- links to
(1 links to)