-
-
Notifications
You must be signed in to change notification settings - Fork 135
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
Implement 'mostly' in expression tests #11
Comments
Apologies if this is addressed elsewhere, but this looks like the closest issue. For the expect_grouped_row_values_to_have_recent_data test, I have one group that will not have recent data for valid reasons. Currently the test fails, saying |
Hi @seanpwlms ! I think this might actually be supported in the new dbt test configs: |
@clausherther Thank you! Of course the answer is to read the docs. Adding |
I tried using the - name: name_tracker
tests:
- dbt_expectations.expect_column_values_to_be_in_set:
value_set: ["ssc", "sp2", "cf", "ssc1"]
+severity: warn
and - name: name_tracker
tests:
- dbt_expectations.expect_column_values_to_be_in_set:
value_set: ["ssc", "sp2", "cf", "ssc1"]
+warn_if: "!=0"
Any idea what the problem could be ? |
I could solve my own problem. - name: name_tracker
tests:
- dbt_expectations.expect_column_values_to_be_in_set:
value_set: ["ssc", "sp2", "cf", "ssc1"]
severity: warn I hope it might help others. |
@rfortmann-ewolff glad you solved it! I think the |
We should support the
mostly
parameter in expression tests as a float that controls what % of rows need to satisfy the given expression test. Default is 100%.The text was updated successfully, but these errors were encountered: