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
ADAP-850: Support test results as a view #8653
ADAP-850: Support test results as a view #8653
Changes from 8 commits
718b892
d4dfec8
e999ed2
f5e0797
8e366bb
1a3bd81
7b4be33
a149d66
0313904
ccf199c
f76fc74
9a0656f
40b646b
661c5f6
3fa0858
49b797e
069a9b2
61d514b
beb0ed4
5aa2031
9971be7
3ddc7d4
4b81e22
0833774
eb1f3b4
cf86565
2f1aa91
96d18a9
c214595
0baf090
1b1d9c6
6c93e34
a47e59e
86b2793
90792e0
c09b81d
729d939
9d3fb06
e70dca3
8b8f9bb
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
Check warning on line 987 in core/dbt/contracts/graph/nodes.py
Codecov / codecov/patch
core/dbt/contracts/graph/nodes.py#L987
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.
here's my read on the logic
relation_type
is configured, then depending on the argument materialize a table or viewshould_store_failures
do all that jazz.the first thing reads to me effectively as a sub-materialization, that is independent of that. so might i be able to pass
should_store_failures() and relation_type='table'
? what happens then?I'm down with a deprecation in the future, but in the meantime might be deprecate the implementation and make
config.get('store_failures')
implyrelation_type='table'
? then there's only one code path for creating a table and storing test results, and the logic within the L30 conditional can be removed?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.
It will create it as a table. This is the same as omitting the 'table' piece entirely.
That's the conclusion that @colin-rogers-dbt and I reached as well. That alters the feature request slightly, but it makes much more intuitive sense. The feature request is now effectively:
I know
store_failures
creates the results as as table, but I want to make it create the results as a view.Instead of implementing a feature alongside
store_failures
, we're augmentingstored_failures
itself.Check warning on line 247 in core/dbt/parser/generic_test_builders.py
Codecov / codecov/patch
core/dbt/parser/generic_test_builders.py#L247
Check warning on line 302 in core/dbt/parser/generic_test_builders.py
Codecov / codecov/patch
core/dbt/parser/generic_test_builders.py#L301-L302