Prototype: test
materialization that allows materialization
to be set in the config()
#8748
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.
regarding #6914
🚧 This is a prototype. It currently includes logging statements an inline comments for demo purposes.
Problem
The failures of dbt tests can only be done ephemerally or stored in a table stored in a table; there is no way to capture test results as a view or a materialized view. So users need to re-run
dbt test
(ordbt build
) to see the results that are up-to-date. Of course those results can immediately go stale 😬Solution
Big idea
Enable test results as a view or a materialized view via the
materialized
config so that they will always show the current failures without the need to run dbt.Users can specify the materialization within the config block in their tests like any the following:
materialized="table"
(isomorphic to--store-failures
)materialized="view"
NEWmaterialized="materialized_view"
NEWImplementation details
Flesh out the ideas in this Loom by combining #8653 with the approach used by the
clone
materialization (introduced in #7881).Checklist