average-dinner-25106
10/13/2022, 10:03 AMmicroscopic-mechanic-13766
10/13/2022, 11:02 AMaction_list:
- name: store_validation_result
action:
class_name: StoreValidationResultAction
- name: store_evaluation_params
action:
class_name:StoreEvaluationParametersAction
- name: update_data_docs
action:
class_name: UpdateDataDocsAction
site_names: []
- name: datahub_action
action:
module_name: datahub.integrations.great_expectations.action
class_name: DatahubValidationAction
server_url: <http://datahub-gms:8080>average-dinner-25106
10/14/2022, 1:01 AMmicroscopic-mechanic-13766
10/17/2022, 7:49 AMaverage-dinner-25106
10/17/2022, 8:21 AMmicroscopic-mechanic-13766
10/17/2022, 8:29 AMgreat_expectations init as far as I know just creates the needed directory structure for Great Expectations to work correctly.
Creating the suite of expectations can sometimes be a nightmare. As I guess you are not very familiar with it (as it is also my case), I would recommend to follow this steps:
• great_expectations suite new --no-jupyter
• Select option 3- Automatically, using a profiler
• Indicate file name
• jupyter notebook /great_expectations/uncommitted/edit_<file_name> --allow-root --ip 0.0.0.0
I would also recommend you to create the files via jupyter notebook, as it gives out more info, is easier,...
(The last command would be to be able to access jupyter in your browser and to use Jupyter's UI to create mentioned files)