Materialized views are fully refreshed about dbt-risingwave HOT 2 CLOSED

Different from other OLAP databases or data warehouses, they use dbt to do ELT. RisingWave is a streaming database, that can maintain a streaming pipeline incrementally in real-time, so you just need to run dbt run once unless you modify your models. That is the difference between an OLAP database and a streaming database.

from dbt-risingwave.

I agree with the idea that RisingWave should not recreate materialized views and tables on each dbt run, unless the user specify '--full-refresh' or '-f'. https://docs.getdbt.com/reference/commands/run

Here is the prototype code that we can express it.

  {%- set old_relation = adapter.get_relation(database=database, schema=schema, identifier=identifier) -%}
  {%- set exists_as_materialized_view = (old_relation is not none and old_relation.is_materialized_view) -%}

  {%- if exists_as_materialized_view or should_full_refresh() -%}
    -- If there's a table with the same name and we were told to full refresh, drop it.
    -- build model
    {% call statement('main') -%}
      {{ get_create_materialized_view_as_sql(target_relation, sql) }}
    {%- endcall %}
  {%- endif -%}

from dbt-risingwave.