Re: [I] Iceberg 1.10.0: Unexpected S3 checksum validation despite s3.checksum-enabled=false [iceberg]

["kamijin-fanta (via GitHub)" <gi...@apache.org>]

kamijin-fanta commented on issue #14439:
URL: https://github.com/apache/iceberg/issues/14439#issuecomment-3561096219

   Like @ochanism, I’ve also been investigating the behavior with S3-compatible object storage. In conclusion, setting `client.legacy-md5-plugin-enabled` has been very effective in my case.
   
   With this enabled, the `Content-MD5` header is included again as before, and in some requests the `Content-Encoding: aws-chunked` header is removed so that they become plain (non-chunked) requests. It also seems that specifying `AWS_REQUEST_CHECKSUM_CALCULATION=when_required` has limited effect, because some of the S3 APIs that Iceberg calls require checksum calculation at the endpoint level anyway.
   
   Of course, the behavior will likely vary depending on the storage implementation. However, I’m leaving this here in case it helps others resolve similar issues.
   


-- 
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: issues-unsubscribe@iceberg.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For additional commands, e-mail: issues-help@iceberg.apache.org