-
Notifications
You must be signed in to change notification settings - Fork 16.3k
Add deferrable option to EmrTerminateJobFlowOperator #31646
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 deferrable option to EmrTerminateJobFlowOperator #31646
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
&& same remarks as on #31657 for the trigger:
- no need to cache hook
- should raise error directly
7788400 to
90338fb
Compare
|
Sorry for tagging everyone in the PR. I messed up my commits 😅 |
bfefcbf to
757e718
Compare
vandonr-amz
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lessgo
Add unit tests
…erminateJobFlowOperator Add EmrTerminateJobFlowTrigger to provider.yaml Address PR comments
Raise error directly from Trigger
849cda4 to
6422a38
Compare
Deferrable mode for
EmrTerminateJobFlowOperatoras well as the associated tests.^ 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.rstor{issue_number}.significant.rst, in newsfragments.