azure_* session settings

ClickHouse session settings in the azure_* generated group.

These settings are available in system.settings and are autogenerated from source.

azure_allow_parallel_part_upload

Use multiple threads for azure multipart upload.

azure_check_objects_after_upload

Check each uploaded object in azure blob storage to be sure that upload was successful

azure_connect_timeout_ms

Connection timeout for host from azure disks.

azure_create_new_file_on_insert

Enables or disables creating a new file on each insert in azure engine tables

azure_ignore_file_doesnt_exist

Ignore absence of file if it does not exist when reading certain keys.

Possible values:

• 1 — SELECT returns empty result.
• 0 — SELECT throws an exception.

azure_list_object_keys_size

Maximum number of files that could be returned in batch by ListObject request

azure_min_upload_part_size

The minimum size of part to upload during multipart upload to Azure blob storage.

azure_request_timeout_ms

Idleness timeout for sending and receiving data to/from azure. Fail if a single TCP read or write call blocks for this long.

azure_skip_empty_files

Enables or disables skipping empty files in S3 engine.

Possible values:

• 0 — SELECT throws an exception if empty file is not compatible with requested format.
• 1 — SELECT returns empty result for empty file.

azure_strict_upload_part_size

The exact size of part to upload during multipart upload to Azure blob storage.

azure_throw_on_zero_files_match

Throw an error if matched zero files according to glob expansion rules.

Possible values:

• 1 — SELECT throws an exception.
• 0 — SELECT returns empty result.

azure_truncate_on_insert

Enables or disables truncate before insert in azure engine tables.

azure_use_adaptive_timeouts

When set to true than for all azure requests first two attempts are made with low send and receive timeouts. When set to false than all attempts are made with identical timeouts.

azure_validate_etag_on_read

When reading a blob from Azure Blob Storage through the azureBlobStorage / azureBlobStorageCluster table functions or the AzureBlobStorage table engine, pin every GET request to the generation of the blob that was observed when it was listed by sending its ETag in If-Match, and check the ETag of the response. A single file read issues many ranged GET requests; if the blob is overwritten in place between them (for example by an external writer rewriting a fixed key), the reads can otherwise be stitched together from two different generations of the blob and surface as a corrupted checksum or parse error. The size recorded at listing time is also used as the right bound of the read, so it is only correct for the generation it was recorded for. When a mismatch is detected the read fails with AZURE_OBJECT_CHANGED_DURING_READ instead of returning inconsistent data. Disable only for workloads that intentionally read blobs that are being overwritten and can tolerate inconsistent reads.