great_expectations.cli.v012.validation_operator
¶
Module Contents¶
Functions¶
Validation Operator operations |
|
|
List known Validation Operators. |
|
Run a validation operator against some data. |
|
-
great_expectations.cli.v012.validation_operator.
json_parse_exception
¶
-
great_expectations.cli.v012.validation_operator.
SQLAlchemyError
¶
-
great_expectations.cli.v012.validation_operator.
validation_operator
() → None¶ Validation Operator operations
-
great_expectations.cli.v012.validation_operator.
validation_operator_list
(directory)¶ List known Validation Operators.
-
great_expectations.cli.v012.validation_operator.
validation_operator_run
(name, run_name, validation_config_file, suite, directory) → None¶ Run a validation operator against some data.
There are two modes to run this command:
Interactive (good for development):
Specify the name of the validation operator using the –name argument and the name of the expectation suite using the –suite argument.
The cli will help you specify the batch of data that you want to validate interactively.
Non-interactive (good for production):
Use the –validation_config_file argument to specify the path of the validation configuration JSON file. This file can be used to instruct a validation operator to validate multiple batches of data and use multiple expectation suites to validate each batch.
Learn how to create a validation config file here: https://great-expectations.readthedocs.io/en/latest/command_line.html#great-expectations-validation-operator-run-validation-config-file-validation-config-file-path
This command exits with 0 if the validation operator ran and the “success” attribute in its return object is True. Otherwise, the command exits with 1.
To learn more about validation operators, go here: https://great-expectations.readthedocs.io/en/latest/features/validation.html#validation-operators
-
great_expectations.cli.v012.validation_operator.
_validate_valdiation_config
(valdiation_config)¶