Open gerrycampion opened 1 year ago
@gerrycampion why not just use variable_name as the target instead with a rule type of Variable Metadata Check:
i.e:
Check:
all:
- name: variable_name
operator: not_contains_all
value:
- $required_variables
I get that we may want to fix this, but is the rule actually blocked by this bug?
No, that should work, thanks. I updated the issue title
Can I ask variable_name gives the list of all the variables in the dataset? If yes it is very unclear
Can I ask variable_name gives the list of all the variables in the dataset? If yes it is very unclear
variable_name is one of the metadata variables available when using the Variable Metadata Check rule type.
The Variable Metadata Check
rule type produces a data frame containing one record for each variable in the current dataset. At the dataset level, you are correct that variable_name
gives the list of all variables in the dataset. This means that at the record level, variable_name
gives the name of the variable of the current record.
@ab3263266
Links to related JIRA Tickets
Rule Information
Describe the bug
not_contains_all
operator not working correctly withget_column_order_from_dataset
operation. Refer to CG0014 (A) in the rule editor and corresponding negative test data.get_column_order_from_dataset
appears to return a list object, butnot_contains_all
expectsself.value[target]
to be a series object in order to applyunique()
.Error returned from Rule Engine
Expected behavior No errors. The rule should return no issues when all required variables exist or return an issue for missing required variables.