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
Call adapter.pre_model_hook + adapter.post_model_hook within tests #10258
Call adapter.pre_model_hook + adapter.post_model_hook within tests #10258
Changes from all commits
ef67cff
c8620c7
62280b2
09ead95
7648500
3e35e91
c15cc74
1b2c839
ca29c03
685ccdb
928e63f
fa98fbd
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
Check warning on line 129 in core/dbt/task/test.py
Codecov / codecov/patch
core/dbt/task/test.py#L129
Check warning on line 147 in core/dbt/task/test.py
Codecov / codecov/patch
core/dbt/task/test.py#L147
Check warning on line 149 in core/dbt/task/test.py
Codecov / codecov/patch
core/dbt/task/test.py#L149
Check warning on line 151 in core/dbt/task/test.py
Codecov / codecov/patch
core/dbt/task/test.py#L151
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.
To confirm, this is not a behaviour change because:
snowflake_warehouse
would always want to route tests to that warehouse?cc @jtcohen6
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.
I think i can help supply a answer here. with this pr and
as tested in dbt-labs/dbt-snowflake#1070
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.
ah! gotcha -- so configs were not possible to provide for generic tests in the past, which means there should not be any currently set on them
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.
from my understanding yes, we could use a old pattern to set a set number of accepted configs linked in the generic_config issue, making this update to the newer syntax while maintaining the old will allow us to do this now.
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 @MichelleArk @McKnight-42 for thinking of this!
As I see it, the only way in which this could be a "breaking" change is if someone had configured a singular test, or all tests (from
dbt_project.yml
), with asnowflake_warehouse
that they didn't actually want to be used.Something like:
I do not see that as a breaking change; I see it as this feature in dbt (specifically
dbt-snowflake
) finally working as intended. As such, I do not believe we need to put it behind a legacy behavior migration flag.Check warning on line 207 in core/dbt/task/test.py
Codecov / codecov/patch
core/dbt/task/test.py#L207
Check warning on line 235 in core/dbt/task/test.py
Codecov / codecov/patch
core/dbt/task/test.py#L235