Introduces distinct error messages for S3 'no key' errors, differentiating between disk-level and storage-level causes.
Why it matters
This feature improves error diagnostics by providing clearer, more specific messages when an S3 'no key' error occurs. It helps users and administrators quickly identify whether the issue is related to local disk problems or the S3 storage itself, facilitating faster troubleshooting and resolution.How to use it
The feature is automatically enabled as part of the ClickHouse S3 integration error handling. Users will receive more precise error messages without additional configuration required.