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 | |
---|---|---|---|---|
DBT run with 4 threads causing AccessExclusiveLock in Redshift | 0 | 3243 | October 13, 2021 | |
DBT AccessExclusiveLock with more than 1 Thread | 0 | 446 | April 24, 2024 | |
DBT Serialization Errors | 0 | 1586 | February 14, 2023 | |
Redshift view deadlocks? | 4 | 2152 | March 14, 2023 | |
DBT, concurrent runs and the need for locking | 1 | 4552 | April 8, 2022 |