v.22.3Improvement

Fix AWS SDK Bug that Set Incorrect Content Type for Large Files Written with S3 Table Function

Official CH changelog text
When large files were written with s3 table function or table engine, the content type on the files was mistakenly set to application/xml due to a bug in the AWS SDK. This closes #33964. #34433 (Alexey Milovidov).
Fixes the content type for large files written using the s3 table function or table engine, correcting it from an incorrect application/xml to the appropriate content type.

Why it matters

When writing large files to S3 via ClickHouse, the files were incorrectly marked with the content type application/xml due to a bug in the AWS SDK. This fix ensures that the content type is set correctly, preventing potential issues with file handling and integration with other services consuming these files.

How to use it

No user action is required to enable the fix. The correction is applied internally when writing files with the s3 table function or table engine, ensuring the proper content type is set automatically.

Related resources

PreviousNext