-
Notifications
You must be signed in to change notification settings - Fork 14.4k
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
Add template_field to DataplexGetDataQualityScanResultOperator #40041
Conversation
Add job_id to template_fields, in order to easily provide returned value from DataplexRunDataQualityScanOperator (the returned value is the triggered job_id), to avoid List operations
Update dataplex.py
Congratulations on your first Pull Request and welcome to the Apache Airflow community! If you have any issues or are unsure about any anything please check our Contributors' Guide (https://github.com/apache/airflow/blob/main/contributing-docs/README.rst)
|
Awesome work, congrats on your first merged pull request! You are invited to check our Issue Tracker for additional contributions. |
Congrats @amirmor1! 🎉 |
Add job_id to template_fields, in order to easily provide returned value from DataplexRunDataQualityScanOperator (the returned value is the triggered job_id), to avoid List operations
Add job_id to template_fields, in order to easily provide returned value from DataplexRunDataQualityScanOperator (the returned value is the triggered job_id), to avoid List operations
Add job_id to template_fields, in order to easily provide returned value from DataplexRunDataQualityScanOperator (the returned value is the triggered job_id), to avoid List operations
Added template_field 'job_id' in DataplexGetDataQualityScanResultOperator since the job_id is a returned value from DataplexRunDataQualityScanOperator, giving the ability to trigger DataplexGetDataQualityScanResultOperator without the need for it to make List requests to Dataplex API
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rst
or{issue_number}.significant.rst
, in newsfragments.