-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Use old_relation for renaming in default materializations #3547
Conversation
…nage changes from view to table and reverse
I checked locally and the only failed test is test/integration/004_simple_snapshot_test/test_simple_snapshot.py, which I doubt is influenced by my changes on table and view materializations. |
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, @danielefrigo! You're right, the failing test was something flakey/unrelated.
Two tiny changes to the Changelog, then this is good to go.
@danielefrigo When you get a chance, could you resolve conflicts / update the changelog? Then this is good to go! |
Co-authored-by: Jeremy Cohen <jtcohen6@gmail.com>
sorry for the delay, I've been on vacation with no chance to work on it. |
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 @danielefrigo !
resolves #2161
Description
change renamed relation to make sure dbt generates the right alter ... rename statement is the materilization type has changed from previous model run
Checklist
CHANGELOG.md
and added information about my change to the "dbt next" section.