[HDDS-9680] Use md5 hash of multipart object part's content as ETag

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Implemented
• Affects Version/s: 1.4.0
• Fix Version/s: 1.5.0
• Component/s: Ozone Manager, S3
• Labels: pull-request-available
• Assignee: Vyacheslav Tutrinov
• Reporter: Vyacheslav Tutrinov
• Created: 13/Nov/23 09:55
• Updated: 20/Feb/24 08:31
• Resolved: 13/Feb/24 09:24

Description

In the scope of HDDS-9114 and HDDS-9115 a support of 'ETag' was implemented. But for the parts of multipart uploaded keys the implementation wasn't changed - the ETag refers to the part's key path and it's not an md5 hash of its content.
It means that another part (e.g. on rewriting the big key) can have the same path (aka 'ETag') but its content can differ from the previous one, it follows that the 'ETag' property of the part should differ too which is not true in the described case.
The improvement should provide a way of computing the parts' paths based on md5-calculated ETags on commiting the multipart upload operation

Issue Links

• is related to: HDDS-10395 Fix eTag compatibility issues during MPU
• relates to: HDDS-9114 Provide ETag in a response header on file uploading through s3g
• relates to: HDDS-9115 Provide ETag in a response header on file downloading through s3g
• links to: GitHub Pull Request #5668