-
Notifications
You must be signed in to change notification settings - Fork 985
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
Fix store_failures
schema documentation
#5047
Changes from all commits
686e61d
c15ea62
a1cef9f
c528025
7cf1e74
996f208
a56df2f
efe1446
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -10,7 +10,7 @@ Optionally set a test to always or never store its failures in the database. | |
- If specified as `true` or `false`, the | ||
`store_failures` config will take precedence over the presence or absence of the `--store-failures` flag. | ||
- If the `store_failures` config is `none` or omitted, the resource will use the value of the `--store-failures` flag. | ||
- When true, `store_failures` saves all the record(s) that failed the test only if [limit](/reference/resource-configs/limit) is not set or if there are fewer records than the limit. `store_failures` are saved in a new table with the name of the test. | ||
- When true, `store_failures` saves all records (up to [limit](/reference/resource-configs/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](/reference/resource-configs/schema#tests) the schema suffix to a different value. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Hiya @brunokim, Thanks for flagging this. This looks really good. I have no changes or suggestions on my end. I'll also look at the merge conflict for you. Kind Regards There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. hey @brunokim and @nataliefiann , fixed up the merge conflict! |
||
- A test's results will always **replace** previous failures for the same test, even if that test results in no failures. | ||
- By default, `store_failures` uses a schema named `dbt_test__audit`, but, you can [configure](/reference/resource-configs/schema#tests) the schema to a different value. Ensure you have the authorization to create or access schemas for your work. For more details, refer to the [FAQ](#faqs). | ||
|
||
|
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.
Hiya @brunokim
This is really good and great use of the example!
Kind Regards
Natalie