[Bug] Full refresh not deleting materialized view with cascade
Dnirmania opened this issue · comments
Dnirmania commented
Is this a new bug in dbt-redshift?
- I believe this is a new bug in dbt-redshift
- I have searched the existing issues, and I could not find an existing issue for this bug
Current Behavior
If execute dbt run --models mv1 --full-refresh
, dbt try to drop mv with drop materialized view if exists "database"."schema"."mv1";
command
Expected Behavior
If execute dbt run --models mv1 --full-refresh
, dbt try to drop mv with drop materialized view if exists "database"."schema"."mv1" cascade;
command
Steps To Reproduce
- Create mv1 materialized view.
- Create mv2 materialized view on top of mv1.
- Execute `dbt run --models mv1 --full-refresh.
Relevant log output
No response
Environment
- OS: ubuntu
- Python: 3.10
- dbt-core: 1.7.1
- dbt-redshift: 1.7.1
Additional Context
No response