vtutrinov commented on PR #5162:
URL: https://github.com/apache/ozone/pull/5162#issuecomment-1671168624
> > provide multipart uploaded file's ETag as a last part's one and save it
to the file metadata storage
>
> Does S3 use the same logic?
@myskov This part of the AWS S3 API is not documented strictly. It says that
an ETag response header of each uploaded file part is equal to {someHash (can
be an MD5 hash)}-{partNumber}. The current implementation of an ETag response
header for file parts in ozone/s3g is pretty much the same, the header value is
equal to {keyPrefix}{keyName}-{someUUID}-{commitTimestamp}-{partNumber}, that's
equal to *partName* (from
org.apache.hadoop.ozone.om.helpers.OmMultipartCommitUploadPartInfo). The final
version of an ETag in AWS S3 API is represented as {hash (the algo of a hash
function is not strictly defined) }-{partscCount}, hence an approach to present
the ETag as {finalPartName}-{partsCount} could be applicable. But it's not a
big deal to replace it by {md5(partNames)}-{partsCount}
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
