The profile_wh_tables can be a massive model to materialize and probably shouldn't be re-built on each run, especially when doing development. For an implementation of the framework, I've tagged that model as manual and run dbt by excluding that tag. Might not be the best solution, but we should have more control into when that table is to materialized.
Tagging:
{{ config(
tags=["manual"]
) }}
Execution
dbt run --exclude tag:manual
┆Issue is synchronized with this Jira Task by Unito
The
profile_wh_tablescan be a massive model to materialize and probably shouldn't be re-built on each run, especially when doing development. For an implementation of the framework, I've tagged that model as manual and run dbt by excluding that tag. Might not be the best solution, but we should have more control into when that table is to materialized.Tagging:
Execution
┆Issue is synchronized with this Jira Task by Unito