hevinhsu commented on PR #9612: URL: https://github.com/apache/ozone/pull/9612#issuecomment-3747583971
Thanks @jojochuang for pointing this out. I agree that the final ETag may not always be an MD5 (especially for multipart or encrypted objects). However, this patch focuses on in-transit integrity checking via the `Content-MD5` header. During the upload, S3G calculates the MD5 of the incoming data stream to verify it against the client-provided `Content-MD5`. This verification happens before the object is committed. The document you shared refers to the ETag's behavior after the commit, which is independent of the `Content-MD5` validation logic at the ingestion stage. Therefore, the ETag's final format does not affect this check. -- 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]
