You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As the thread title says, I see no reason why this is not an option. Imagine an scenario where you want to store rows that failed a test. At the moment, [ the documentations says: When true, store_failures saves all records (up to limit) that failed the test. Failures are saved in a new table with the name of the test. By default, store_failures uses the schema {{ profile.schema }}_dbt_test__audit, but you can configure the schema suffix to a different value. ](https://docs.getdbt.com/reference/resource-configs/store_failures).
I would like to store the rows that failed the test and if possible, have some sort of scd to see whether the record that failed the test is still failing the test upon fixing the upstream.
Another use case that I can think of is quarantining the rows by storing the failures, and filter the model itself from the quarantine values, it would look something like this:
model test > model stores failures > model runs omitting the values that were quarantined.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
As the thread title says, I see no reason why this is not an option. Imagine an scenario where you want to store rows that failed a test. At the moment, [ the documentations says: When true, store_failures saves all records (up to limit) that failed the test. Failures are saved in a new table with the name of the test. By default, store_failures uses the schema {{ profile.schema }}_dbt_test__audit, but you can configure the schema suffix to a different value. ](https://docs.getdbt.com/reference/resource-configs/store_failures).
I would like to store the rows that failed the test and if possible, have some sort of scd to see whether the record that failed the test is still failing the test upon fixing the upstream.
Another use case that I can think of is quarantining the rows by storing the failures, and filter the model itself from the quarantine values, it would look something like this:
model test > model stores failures > model runs omitting the values that were quarantined.
Beta Was this translation helpful? Give feedback.
All reactions