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
Looking at your check, I am wondering if it is the expected behavior missing_percent(my_column_name) < 100%, this means you are expecting all values to be null. In this case, it is not so it fails.
Aren't you looking for the following check: missing_percent(my_column_name) < 0% ?
missing_percent(my_column_name) < 0% would ensure that I had 0 missing data and that single row was not NULL.
That's not my intention with this check, I want to make sure that at least some rows are non-NULL.
I lowered my threshold and looked at another column, to demonstrate. Here I will say that less than 65% NULL is acceptable, any higher and that's bad.
checks for my_table_name [daily]:
- missing_percent(my_other_column_name) < 65%:
name: Feature column my_other_column_name contains values that are not NULL
Here is my check:
My data is nearly all NULL, but not entirely.
I have a very small percentage of non NULL values, so my check should pass, however it fails because I assume there is some rounding.
0.999984 != 1.
The text was updated successfully, but these errors were encountered: