-
Notifications
You must be signed in to change notification settings - Fork 104
fix: check for old tmp table before deleting it #550
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
Conversation
39b10d0
to
7da1c6d
Compare
@octiva Could you double check if we need to adapt also anything in the incremental part? maybe we can benefit for the same approach too, that seems more resilient and correct. |
dbt/include/athena/macros/materializations/models/incremental/incremental.sql
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for this improvement @octiva 💯
@svdimchenko / @Jrmyy could you have another look?
dbt/include/athena/macros/materializations/models/incremental/incremental.sql
Outdated
Show resolved
Hide resolved
62d6801
to
38937bf
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for your contribution @octiva
Happy to contribute! |
Description
Implemented as discussed in #546.
Uses
adapter.get_relation
to search for an old tmp_relation that could exist if the previous table creation did not clean it up properly.Models used to test - Optional
Checklist