In my project, I’ve built several incremental materialized fact models on top of snapshot tables. However, during model execution, if downstream teams query these fact tables in Redshift, the models often enter a locked state and continue running indefinitely unless the tasks are externally terminated. Similar to how late binding works with views, is there a way to prevent such locking behavior for incremental models(tables)
Related topics
Topic | Replies | Views | Activity | |
---|---|---|---|---|
How to configure dbt to only incrementally process values it has not processed before? | 2 | 2044 | March 24, 2024 | |
On the limits of incrementality | 17 | 71042 | November 2, 2023 | |
dbt incremental models not working | 1 | 163 | May 6, 2025 | |
Incremental model runs only like "create or replace table..." | 6 | 3999 | October 24, 2023 | |
Data not being incremented on dbt run | 6 | 2507 | February 6, 2024 |