Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Workaround for bug when AWS mistakenly set Content-Type to XML #34433

Merged
merged 8 commits into from
Feb 17, 2022

Conversation

alexey-milovidov
Copy link
Member

Changelog category (leave one):

  • Improvement

Changelog entry (a user-readable short description of the changes that goes to CHANGELOG.md):
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.

@robot-clickhouse robot-clickhouse added the pr-improvement Pull request with some product improvements label Feb 9, 2022
@alexey-milovidov alexey-milovidov marked this pull request as ready for review February 9, 2022 02:56
@kitaisreal kitaisreal self-assigned this Feb 9, 2022
@kitaisreal
Copy link
Contributor

Need to fix flaky test 02207_s3_content_type.

@alesapin alesapin self-assigned this Feb 15, 2022
@alesapin
Copy link
Member

Waiting only for flaky check.

@alesapin
Copy link
Member

Finally!

02207_s3_content_type | OK | 1.85
-- | -- | --

@alesapin alesapin merged commit 6df2c9c into master Feb 17, 2022
@alesapin alesapin deleted the s3-fix-content-type branch February 17, 2022 10:11
@@ -10,15 +10,4 @@ $CLICKHOUSE_CLIENT --query "
INSERT INTO TABLE FUNCTION s3('http://localhost:11111/test/content-type.csv.gz', 'test', 'testtest', 'CSV', 'number UInt64') SELECT number FROM numbers(1000000) SETTINGS s3_max_single_part_upload_size = 10000, s3_truncate_on_insert = 1;
"

# strace -e trace=network,write -s1000 -f ~/work/ClickHouse/mc cat clickminio/test/content-type.csv.gz >/dev/null
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What was wrong with this command, just curious?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pr-improvement Pull request with some product improvements
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Wrong s3 object content type for large files
4 participants