ivandika3 commented on PR #9612: URL: https://github.com/apache/ozone/pull/9612#issuecomment-3762666502
> The ETag may or may not be an MD5 digest of the object data. Yes, ETag can technically be any hash that based on the object data so it doesn't need to be MD5. Moreover, object uploaded using multipart upload ETag is a hash of all the ETag of all the parts with the "-<num_parts>" prefix, see `S3MultipartUploadCompleteRequest#multipartUploadedKeyHash`. If we decide in the future to change ETag to not be md5 hash, then we need to setup a new MD5 `MessageDigest`. However, since ETag is currently already using MD5, we can piggy back that. -- 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]
