Skip to content

Conversation

@chirodip98
Copy link
Contributor

@chirodip98 chirodip98 commented Jan 3, 2026

Fixes : #59812 (comment)
In Case of Cluster does not exists , DataprocDeleteClusterOperator will simply log meaningfull message and will exit.

Copy link
Contributor Author

@chirodip98 chirodip98 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@shivannakarthik , @VladaZakharova and @MaksYermak Can you review now?

@chirodip98
Copy link
Contributor Author

chirodip98 commented Jan 3, 2026

dataproc_delete_cluster_test.html

System Test Logs - Updated

Copy link
Contributor

@jscheffl jscheffl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good from reading but really would be good having a review from one of the Google team members as well

@shahar1
Copy link
Contributor

shahar1 commented Jan 3, 2026

cc: @VladaZakharova

@shahar1 shahar1 changed the title FIX: DataprocDeleteClusterOperator to raise AirflowSkipException if the cluster is already Deleted / Not Found DataprocDeleteClusterOperator to raise AirflowSkipException if the cluster is already Deleted / Not Found Jan 3, 2026
@chirodip98
Copy link
Contributor Author

chirodip98 commented Jan 5, 2026

  • Added deferable test cases
  • Corrected the timezone (airflow.util.timezone is non-existent , falling back to airflow.sdk.timezone)
  • Updated System Test (reports updated)

Requesting review : @MaksYermak @VladaZakharova

@chirodip98
Copy link
Contributor Author

Can anyone help / suggest why the test are failing?
https://github.com/apache/airflow/blob/main/airflow-core/src/airflow/utils/__init__.py

@chirodip98 chirodip98 changed the title DataprocDeleteClusterOperator to raise AirflowSkipException if the cluster is already Deleted / Not Found DataprocDeleteClusterOperator to log message and not cause failure, if the cluster is already Deleted / Not Found. Jan 5, 2026
jason810496 and others added 9 commits January 9, 2026 09:43
…pache#60259)

* Initial plan

* Add portForward section to _build_skaffold_config for API server

Co-authored-by: jason810496 <68415893+jason810496@users.noreply.github.com>

* Add kubectl section instead of portForward section

* Fix: hooks should place under helm instead of kubectl

---------

Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
* refactor: Implemented BaseAsyncOperator in task-sdk

* refactor: Now PythonOperator extends BaseAsyncOperator

* refactor: Also implement BaseAsyncOperator in common-compat provider to support older Airflow versions

---------

Co-authored-by: Jason(Zhe-You) Liu <68415893+jason810496@users.noreply.github.com>
…pache#59883)

Extract the listeners infrastructure to `shared/listeners/` library to eliminate cross dependencies between airflow-core and task-sdk.

- ListenerManager and hookimpl marker now in shared library
- Hook specs split by callers:
  - shared: lifecycle, taskinstance (called from both sdk and core)
  - core: dagrun, asset, importerrors (called only from core)
- sdk registers only specs it actually uses (lifecycle, taskinstance)
- core registers all specs for full listener support
* Refactor airflow-core/tests cli commands to use SQLA2

* Refactor airflow-core/tests cli commands to use SQLA2
…pache#60264)

When installing Airflow 2 in Breeze, we need to add pydantic as
extra, because pydantic in Airflow 2 was not a required dependency
and installation of airflow even with constraints willl not
downgrade pydantic to the version that was supported in Airflow 2.

When we detect that airflow 2 is installed (either by specified
version number or by retrieving the version from the dist package)
we simply extend the extras with pydantic and that causes airflow
installation to downgrade pydantic to the version that is specified
in constraints of selected airflow version.
…tests. (apache#60027)

Co-authored-by: Sameer Mesiah <smesiah971@gmail.com>
@chirodip98
Copy link
Contributor Author

kindly approve workflows

@shahar1 shahar1 self-requested a review January 10, 2026 08:24
@shahar1
Copy link
Contributor

shahar1 commented Jan 10, 2026

kindly approve workflows

It seems that workflows were approved.
Please fix the PR according to Vlada's comments, thanks!

@chirodip98
Copy link
Contributor Author

Can we have review @VladaZakharova @shivannakarthik @shahar1 .
I have refactored the code.

@shahar1
Copy link
Contributor

shahar1 commented Jan 12, 2026

My approval is a bit hesitated - IMO we should have an explicit flag for that (something like ignore_is_missing in Microsoft azure operator), as I could imagine some edge scenarios where actions are taken upon "not found" entities.
However, considering the benefits for solving the issue in discussion and the fact that in other GCP operators we already catch NotFound error, I'm ok with merging it as-is for now.
I'll put this matter into a discussion in the dev. list, and we could add this flag later if the community finds it necessary.

@shahar1 shahar1 changed the title DataprocDeleteClusterOperator to log message and not cause failure, if the cluster is already Deleted / Not Found. Make DataprocDeleteClusterOperator idempotent Jan 12, 2026
@shahar1 shahar1 merged commit bd133c0 into apache:main Jan 12, 2026
89 checks passed
@boring-cyborg
Copy link

boring-cyborg bot commented Jan 12, 2026

Awesome work, congrats on your first merged pull request! You are invited to check our Issue Tracker for additional contributions.

@chirodip98
Copy link
Contributor Author

Let's create a issue to update the documentation for the same accordingly.

@chirodip98 chirodip98 deleted the fix/59812 branch January 13, 2026 02:05
iharsh02 pushed a commit to iharsh02/airflow that referenced this pull request Jan 13, 2026
@shahar1
Copy link
Contributor

shahar1 commented Jan 13, 2026

Let's create a issue to update the documentation for the same accordingly.

Feel free, but please keep in mind that specifically for documentation it's quicker just to create the PR directly instead of creating an issue for that :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:providers provider:google Google (including GCP) related issues

Projects

None yet

Development

Successfully merging this pull request may close these issues.

DataprocDeleteClusterOperator fails if cluster was already deleted by DataprocCreateClusterOperator(delete_on_error=True)