Skip to content

docs: clarify what Beta means for the dbt v2 adapter #775

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
koletzilla merged 2 commits into from
Nov 3, 2026
Merged

docs: clarify what Beta means for the dbt v2 adapter #775

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
2ae8340
docs: clarify what Beta means for the dbt v2 adapter
BentsiLeviav Nov 3, 2026
05bf872
docs: keep the GA timeline open
BentsiLeviav Nov 3, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions docs/dbt-core-v2-fusion-and-platform.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,9 @@ dbt is being rebuilt on a new engine, and ClickHouse is part of that from the st
ClickHouse is the first community adapter on dbt OSS, dbt v2 and the dbt platform. dbt's own first-party adapters are launching alongside us; we are the first from outside dbt Labs. The dbt Core 1.x Python adapter, `dbt-clickhouse`, is not going away: we keep it current with dbt 1.x releases and maintain both adapters in parallel.

<Warning>
**Not production-ready.** The ClickHouse adapter for dbt OSS and dbt v2, and the dbt platform connection, are not yet generally available (GA). Use them only in development or staging projects.
**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.

@canbekley canbekley Nov 3, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

even though we clarify the term in the table below and in the second sentence here, I'm wondering whether dbt OSS can be easily confused with dbt Core 1.x, and whether we can refer to both dbt OSS and dbt v2 as just being dbt v2? wdyt?

@koletzilla koletzilla Nov 3, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I feel like the clarification is what we need for the confusion things you mentioned.

For example mentioning both dbt OSS and dbt v2 can help people differentiate them, specially for these that may be interesting in keeping the use of open source.

@canbekley canbekley Nov 3, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

makes sense. yes I agree, the warning should be clear enough now. lgtm!


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.
</Warning>

<Note>
Expand Down Expand Up @@ -54,7 +56,7 @@ We measure the dbt v2 adapter against the dbt Core 1.x integration test suite of

**Next steps**: `ON CLUSTER` DDL and the distributed materializations for self-managed clusters, grants, `dbt clone`, `dbt source freshness` from table metadata, fixes for the remaining bugs and passing the full v1 test suite to ensure full parity. The progress of all of these is tracked in [ClickHouse/dbt-clickhouse#660](https://github.com/ClickHouse/dbt-clickhouse/issues/660), with one sub-issue per area.

GA is on the roadmap and will come soon. We'll update the docs once it's ready.
GA is on the roadmap. We are working with dbt Labs on the timeline and will update this page when it's ready.

### Out of scope for Beta {#out-of-scope}

Expand Down
Loading