Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Triggering LegacyCheckpoint without 'validation_operator_name' from GreatExpectationsOperator #30

Closed
ShaharPotash1 opened this issue Jun 8, 2021 · 0 comments · Fixed by #32

Comments

@ShaharPotash1
Copy link

@talagluck as I wrote on the Slack channel,
I'm trying to trigger a Slack notification with the GreatExpectationsOperator.
It necessary to use the validation_operator_name to trigger such notification and it is not possible with the current configuration:
https://github.com/great-expectations/airflow-provider-great-expectations/blob/e92a613db94aa872957fa8626f6d5e71690fe421/great_expectations_provider/operators/great_expectations.py#L130

@ShaharPotash1 ShaharPotash1 changed the title Triggering LegacyCheckpoint 'without validation_operator_name' from GreatExpectationsOperator Triggering LegacyCheckpoint without 'validation_operator_name' from GreatExpectationsOperator Jun 9, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
1 participant