-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
dbt run fails when you change the materialization type #221
Comments
@sdebruyn , I tried to repro the issue, but couldn't. Please see the below execution log. I created a model stg_customers.sql as a view, changed it as a table and then as a view. Also, please see the attached dbt log for all three executions.
With dbt-fabric==1.8.7 version
|
So when I have seen this issue one has to make an error within a model causing it to fail. If the user then materializes it opposite of the first time then run it does not drop the opposing dbt_backup materialization. Maybe that is what this originally getting at? |
@TheBishop-98 , good catch. The table materialization should check for backup_relation type using I will update it and release a new version along other changes. |
@prdpsvs When can we expect the fix to be shipped? Some of these small issues are popping up in our production runs, and should not be. |
When you first materialize a model as a view and then later on change your config to materialize that exact same model as a table, it will fail because dbt-fabric tries to drop the model as being a table while it was a view. Other adapters handle this gracefully by dropping the view without issues.
The text was updated successfully, but these errors were encountered: