Skip to content

[dbt-clickhouse] New tip: codec and ttl also available for mvs with implicit targets #5845

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

Open
koletzilla wants to merge 2 commits into
base: main
Choose a base branch
from
Open

[dbt-clickhouse] New tip: codec and ttl also available for mvs with implicit targets #5845

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
5080323
New tip: codec and ttl also available for mvs with implicit targets
koletzilla Mar 25, 2026
a6bca69
Make sure possible table configurations are clear
koletzilla Mar 25, 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: 5 additions & 1 deletion .../integrations/data-ingestion/etl-tools/dbt/materialization-materialized-view.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -60,6 +60,10 @@ GROUP BY event_date, event_type

See the [test file](https://github.com/ClickHouse/dbt-clickhouse/blob/main/tests/integration/adapter/materialized_view/test_materialized_view.py) for additional examples.

:::tip
You can also define column-level `codec` and `ttl` on the target table by enforcing a model contract. See [Column Configuration](/integrations/dbt/materializations#column-configuration) for details.
:::

### Multiple materialized views {#multiple-materialized-views}

ClickHouse allows more than one materialized view to write records to the same target table. To support this in dbt-clickhouse with the implicit target approach, you can construct a `UNION` in your model file, wrapping the SQL for each materialized view with comments of the form `--my_mv_name:begin` and `--my_mv_name:end`.
Expand Down Expand Up @@ -207,7 +211,7 @@ GROUP BY event_date, event_type

### Configuration options {#explicit-target-configuration}

When using explicit target tables, the following configurations apply:
When using explicit target tables, apart from the [general materialization configurations](/integrations/dbt/materializations#general-materialization-configurations) and the [table-specific configurations](/integrations/dbt/materializations#materialization-table), the following configurations apply:

**On the target table (`materialized='table'`):**

Expand Down
Loading