[HDDS-9114] Provide ETag in a response header on file uploading through s3g

• Type: Task
• Status: Resolved
• Priority: Major
• Resolution: Implemented
• Fix Version/s: 1.4.0
• Component/s: S3
• Labels: pull-request-available
• Assignee: Vyacheslav Tutrinov
• Reporter: Vyacheslav Tutrinov
• Created: 03/Aug/23 07:21
• Updated: 05/Apr/24 02:39
• Resolved: 06/Nov/23 18:31

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

Issue Links

• causes: HDDS-10587 Reset the thread-local MessageDigest instance during exception
• contains: HDDS-9115 Provide ETag in a response header on file downloading through s3g
• is a parent of: HDDS-10403 CopyObject should set ETag based on the key content
• is part of: HDDS-792 Use md5 hash as ETag for Ozone S3 objects
• is related to: HDDS-9680 Use md5 hash of multipart object part's content as ETag
• links to: GitHub Pull Request #5162