Perf: Only recreate materialzed views when necessary #546
Labels
aspects v1
Issues blocking Aspects v1 release
bug
Report of or fix for something that isn't working as intended
With the move of MVs to dbt, we currently rebuild every mv table on every dbt run / aspects init. This will be a problem with large datasets over time, we want to only rebuild those tables when absolutely necessary. dbt has the
on_configuration_change
configuration option to support this, we'll need to upstream it to dbt-clickhouse then update.See: https://docs.getdbt.com/docs/build/materializations#materialized-view
The text was updated successfully, but these errors were encountered: