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
Currently, if I wanted to check for null values in each of the columns (age, occupation) of a table, the checks: section of the configuration file would contain something this:
- type: nullCheckcolumn: age
- type: nullCheckcolumn: occupation
Ideally, we should support a more streamlined config. Something like:
- type: nullCheckcolumns: age, occupation
We would need to decide how to handle optional parameters in the streamlined case. One option is that we do not support streamlining if any optional parameters are specified:
Currently, if I wanted to check for null values in each of the columns (
age
,occupation
) of a table, thechecks:
section of the configuration file would contain something this:Ideally, we should support a more streamlined config. Something like:
We would need to decide how to handle optional parameters in the streamlined case. One option is that we do not support streamlining if any optional parameters are specified:
Another option would be to allow additional parameters to be streamlined and applied in the same order as the specified columns:
The text was updated successfully, but these errors were encountered: