Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Ensure that target_schema from snapshot config is promoted to node level #8117
Ensure that target_schema from snapshot config is promoted to node level #8117
Changes from 3 commits
dbd206f
3fd6d5f
80d6267
6ae9994
64b86f8
fa45019
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
For my own understanding: Previously we were calling also
self._update_node_[database|schema|alias]
on snapshots nodes. Were those no-ops and are no longer necessary?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.
This feels like it has holes in it, but I was attempting to mimic the logic in "set_snapshot_attributes" in core/dbt/parser/snapshots.py. Which doesn't actually use the database set in configs, and always just sets "target_schema" (which is required). It also doesn't go through the generate_name code (so that customers have to call the generate_name code directly in their models if they want it).