Open cbuffett opened 2 years ago
Hey @cbuffett Thanks for issue report. I'll be asking the dev team about this. A question though:
Correct. It was disabled using validator_target.interactive_evaluation = False
. This is necessary, otherwise an exception is thrown because the evaluation parameters haven't actually been created in memory yet (this happens when running the checkpoint later on I believe). This is called out in Step 3 of https://docs.greatexpectations.io/docs/guides/expectations/advanced/how_to_create_expectations_that_span_multiple_batches_using_evaluation_parameters/
Describe the bug The static method
validate_metric_value_between_configuration
has checks in place to validate that if the passed in min/max values are dictionaries, that they contain the$PARAMETER
keyword, but then immediately attempts to compare said dictionaries using the>
inequality operator, resulting in an exception:To Reproduce Steps to reproduce the behavior: Attempt to use the expect_column_min_to_be_between expectation with evaluation parameters
Expected behavior Evaluation parameters should be substituted prior to inequality check or dictionaries should be handled separately.
Environment (please complete the following information):
Additional context In this case, interactive evaluation was disabled.