ClickHouse: connection-level settings and HTTP User-Agent identification
dbt now supports ClickHouse connection-level settings including profile custom_settings and synchronous-operation defaults, wires the default database to the profile schema, handles literal '?' in SQL, and identifies itself in HTTP User-Agent headers via the new adbc_clickhouse driver.
2.0.0-dev.37
Released September 09, 2026
Features
- [ClickHouse] Connection-level settings (profile custom_settings plus v1-parity synchronous-operation defaults), default database wired to the profile schema, literal '?' in SQL, and dbt identified as
dbt/<version>in the HTTP User-Agent (system.query_log.http_user_agent), via the new adbc_clickhouse driver (#14585)
Contributors
Source: original entry ↗
More from dbt
Follow dbt to get its new changes in your feed and email digest.
dbt 2.0.0-dev.41
Added Lake Compute support for reading AWS Databricks Unity Catalog tables with PAT/OAuth M2M credentials. Fixed multiple issues including modules.re keyword argument handling, column-tag diffs in Databricks, and test config inheritance from dbt-core.
BigQuery drivers continue on ADBC.GetObjects errors
Fixed an issue where BigQuery drivers would fail on ADBC.GetObjects 404/403 errors, which was causing incorrect use of REPLACE TABLE instead of MERGE for incremental tables. The drivers now continue gracefully when encountering these errors.