-
Notifications
You must be signed in to change notification settings - Fork 16.3k
DataprocDeleteClusterOperator to raise AirflowSkipException if the cluster is already Deleted / Not Found #59854
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
DataprocDeleteClusterOperator to raise AirflowSkipException if the cluster is already Deleted / Not Found #59854
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.
@potiuk kindly review . I am fairly new to contributing to airflow. Look forward to your guidance and feedback!
Guidance no.1 : Please avoid pinging individual maintainers - just open PR. and not ping people. When you ping someone, you significantly decrease your chances of getting review by someone else, and when the person you ping is not available or simply does not want to - for any reason - review it, you might wait for a long time for any review (which might happen anyway, but then you can again ping (in general, not individual maintainer) after few days and that will bring your PR back to the top of the pile of PRs. |
dd10705 to
2f24ab0
Compare
…chirodip98/airflow-contrib into fix/delete-cluster-dataproc-bug
…teClusterOperator
…teClusterOperator
* Compatibility updates for sqlalchemy 2.0 * Fixes for review comments * Fixes for review comments * More fixes for review comments
chirodip98
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.
Need support to run Workfows
|
I approved it but I thin we need a look from @VladaZakharova and @MaksYermak -> Google team, and - ideally a system test log / screenshots on running this operator using system tests for that operation. |
|
Thanks! |
providers/google/src/airflow/providers/google/cloud/operators/dataproc.py
Outdated
Show resolved
Hide resolved
|
|
||
| mock_hook.return_value.wait_for_operation.assert_not_called() | ||
| assert not mock_defer.called | ||
| assert mock_defer.called |
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.
Is this required?
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.
yes
…into fix/delete-cluster-dataproc-bug
0a30780 to
a51e6e1
Compare
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.
Is it okay If I raise a new PR for this issue and close this? I am facing some issues while rebasing. @potiuk
|
closing this as re-opened |






Fixes : (apache/airflow#59812)
In Case of Cluster does not exists , DataprocDeleteClusterOperator will raise AirflowSkipException.