https://docs.aws.amazon.com/AmazonS3/latest/userguide/UsingKMSEncryption.html
Similar to the server_side_encryption_customer_key_base64 option for
configuring SSE-C with S3, add the following settings to configure
SSE-KMS on a per-endpoint/disk basis:
- server_side_encryption_kms_key_id
- server_side_encryption_kms_encryption_context
- server_side_encryption_kms_bucket_key_enabled
The S3 table engine supports specifying extra HTTP headers in S3
requests to certain endpoints, via the "headers" setting. This commit
adds the same setting to S3 disk config.
* master: (331 commits)
Revert "Fix endian issue in integer hex string conversion"
Update sparse-primary-indexes.md to correct typo
to MaterializeMySQL_support_drop_mulit_table-change ParserIdentifier
to MaterializeMySQL_support_drop_mulit_table-clean up unnecessary code
Make insertRangeFrom() more exception safe (#43338)
Update docs/en/sql-reference/statements/create/view.md
Update docs/en/sql-reference/statements/alter/projection.md
Analyzer table functions untuple fix
Revert "Add table_uuid to system.parts"
Update 00176_bson_parallel_parsing.sh
Update test.py
doc fix
bump lib for diag
Update kafka.md
check ast limits for create_parser_fuzzer
Disable compressed marks and index in stress tests
add a test with weird strings
Update .reference
Add information about written rows in progress indicator
Avoid possible DROP hung due to attached web disk
...
