From ed356b4a5159cf130c1cefa40eb6b5d563adda0c Mon Sep 17 00:00:00 2001 From: Anders Swanson Date: Tue, 4 Jun 2024 16:50:31 +0000 Subject: [PATCH] deprecate experimental MVs --- README.md | 6 ++++++ materialized-views/README.md | 5 +++++ 2 files changed, 11 insertions(+) diff --git a/README.md b/README.md index 4dcef52..13ac84d 100644 --- a/README.md +++ b/README.md @@ -11,6 +11,12 @@ In all cases, these are _demo_ projects, not intended as ready-to-use packages. ## [Materialized views](materialized-views) +> [!CAUTION] +> The implementation in this repo is no longer maintained. +> Materialized Views have been fully supported in dbt Cor since version `1.7` (November 2023). +> See [dbt docs: materialized views](https://docs.getdbt.com/docs/build/materializations#materialized-view) for more information. + + This project adds support for `materialized_view` as a new dbt materialization. It includes implementations for Postgres, Redshift, Snowflake, and BigQuery, through a mix of new macros and overrides of built-in dbt macros. See the [project README](materialized-views/README.md) for details. For another take on dbt + materialized views, check out the [dbt-materialize](https://github.com/MaterializeInc/materialize/tree/main/misc/dbt-materialize#dbt-materialize) plugin. ## [Lambda views](lambda-views) diff --git a/materialized-views/README.md b/materialized-views/README.md index 9a928d6..ab4c2ef 100644 --- a/materialized-views/README.md +++ b/materialized-views/README.md @@ -1,5 +1,10 @@ ## dbt_labs_materialized_views +> [!CAUTION] +> The implementation in this repo is no longer maintained. +> Materialized Views have been fully supported in dbt Cor since version `1.7` (November 2023). +> See [dbt docs: materialized views](https://docs.getdbt.com/docs/build/materializations#materialized-view) for more information. + `dbt_labs_materialized_views` is a dbt project containing materializations, helper macros, and some builtin macro overrides that enable use of materialized views in your dbt project. It takes a conceptual approach similar to that of the existing `incremental` materialization: - In a "full refresh" run, drop and recreate the MV from scratch. - Otherwise, "refresh" the MV as appropriate. Depending on the database, that could require DML (`refresh`) or no action.