From 508032348d2995eefb97571e67cca5f89ae221f0 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jose=20Mu=C3=B1oz?= Date: Wed, 25 Mar 2026 11:37:19 +0100 Subject: [PATCH 1/2] New tip: codec and ttl also available for mvs with implicit targets --- .../etl-tools/dbt/materialization-materialized-view.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/integrations/data-ingestion/etl-tools/dbt/materialization-materialized-view.md b/docs/integrations/data-ingestion/etl-tools/dbt/materialization-materialized-view.md index 9d4e91ddc6f..953c00632b1 100644 --- a/docs/integrations/data-ingestion/etl-tools/dbt/materialization-materialized-view.md +++ b/docs/integrations/data-ingestion/etl-tools/dbt/materialization-materialized-view.md @@ -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`. From a6bca69c585157b62bbf719e95d8961c4931ba29 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jose=20Mu=C3=B1oz?= Date: Wed, 25 Mar 2026 16:08:17 +0100 Subject: [PATCH 2/2] Make sure possible table configurations are clear --- .../etl-tools/dbt/materialization-materialized-view.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/integrations/data-ingestion/etl-tools/dbt/materialization-materialized-view.md b/docs/integrations/data-ingestion/etl-tools/dbt/materialization-materialized-view.md index 953c00632b1..aa66100baa5 100644 --- a/docs/integrations/data-ingestion/etl-tools/dbt/materialization-materialized-view.md +++ b/docs/integrations/data-ingestion/etl-tools/dbt/materialization-materialized-view.md @@ -211,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'`):**