Repository navigation
Update v2 status documentation - #780
Merged
Merged
Conversation
koletzilla
commented
Nov 5, 2026
| <Warning> | ||
| **Beta, not yet GA.** The ClickHouse adapter for dbt OSS and dbt v2 is in Beta, and the dbt platform connection is in Private Beta. The dbt Core 1.x adapter, `dbt-clickhouse`, is GA and supported for production use; nothing on this page changes that. | ||
|
|
||
| Beta means that every materialization (including `incremental` with all its strategies), model contracts, data and unit tests and the ClickHouse Cloud feature set work today and pass the dbt Core 1.x integration test suite. The features that are still pending are listed in [v1 vs v2 parity](#parity) and that list shrinks with every release. We recommend evaluating dbt v2 in development or staging first, and keeping production on dbt Core 1.x if your project depends on any of the pending features or you need the guarantees of a GA release. |
Contributor
Author
There was a problem hiding this comment.
Moved to Details on current status
koletzilla
commented
Nov 5, 2026
| | Docs persistence | Descriptions written as ClickHouse comments. | <Badge color="yellow">Partial</Badge> | Descriptions containing `;` fail. | | ||
| | Docs persistence | Descriptions written as ClickHouse comments. | <Badge color="green">Supported</Badge> | | | ||
| | Catalog and docs generation | Column metadata for the docs site. | <Badge color="green">Supported</Badge> | | | ||
| | Column-level lineage | Trace columns through the DAG. | <Badge color="yellow">Partial</Badge> | New in v2 via the SQL compiler, not available in v1. dbt platform lineage renders only with identifier quoting disabled in `dbt_project.yml`; engine-side lineage needs the ClickHouse SQL dialect. | |
Contributor
Author
There was a problem hiding this comment.
Moved to v2 specifics
koletzilla
commented
Nov 5, 2026
| | `dbt clone` | Zero-copy `CLONE AS` between environments. | <Badge color="green">Supported</Badge> | MergeTree tables, seeds, snapshots and incrementals are cloned with `CLONE AS`; views and other engines fall back to views, as in v1. | | ||
| | Query ID in run results | `query_id` in `adapter_response` for `system.query_log` correlation. | <Badge color="red">Not yet</Badge> | | | ||
| | `query-comment` | Query comment configuration. | <Badge color="red">Not yet</Badge> | `query-comment: null` is not honored yet. | | ||
| | Catalog integration (Iceberg) | Materialize into external catalogs. | <Badge color="red">Not yet</Badge> | Not in v1 either; workarounds documented. | |
Contributor
Author
There was a problem hiding this comment.
Not in v1 anyway, and it's documented in the general docs.
koletzilla
commented
Nov 5, 2026
|
|
||
| | Feature | What it does in v1 | Why it is not planned | | ||
| |---------|--------------------|-----------------------| | ||
| | `verify: false` | Skips TLS certificate validation. | It keeps the encryption but drops the authentication, so anyone on the path can impersonate the server and read the credentials. v2 always validates certificates and ignores the key. Use a certificate signed by a CA the client trusts. Open an issue if you need it in v2. | |
Contributor
Author
There was a problem hiding this comment.
Not really needed right now. I think we should wait for users requesting it.
koletzilla
added
the
sync-docs
canbekley
approved these changes
Nov 5, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
verifymoved table with the security rationale.Note
Low Risk
Documentation-only changes with no runtime or adapter code; risk is limited to doc accuracy if status claims drift from reality.
Overview
Updates
docs/dbt-core-v2-fusion-and-platform.mdxto reflect current dbt v2 ClickHouse adapter maturity: integration coverage is now ~98% (270/276) with remaining gaps called out as engine-side (query comments,query_id, hook naming), and the status section is renamed to Details on current status.The v1 vs v2 parity tables are revised so several former gaps are marked Supported (distributed materializations,
ON CLUSTER, grants,dbt clone, docs persistence), while pending work and v2-only capabilities (SQL dialect/static analysis, lineage, Semantic Layer, platform auth, etc.) are split into newNot planned for v2anddbt v2 specific functionalitysections instead of living in the Beta warning/out-of-scope bullets.Reviewed by Cursor Bugbot for commit 2d0ef49. Bugbot is set up for automated code reviews on this repo. Configure here.