shahar1 opened a new issue, #61224: URL: https://github.com/apache/airflow/issues/61224
### Description The Google provider’s Data Fusion integration can start a pipeline and returns a `run_id` (aka “pipeline_id” in Airflow operators), but the stop functionality only stops the program (not a specific run). CDAP/Data Fusion supports stopping a specific run via “Stop a Program Run”, and Airflow should expose that to avoid stopping an arbitrary run when multiple runs are active. ### Use case/motivation In CDAP, workflows can have multiple concurrent runs. The current “Stop a Program” endpoint: `POST /v3/namespaces/<namespace-id>/apps/<app-id>/<program-type>/<program-id>/stop` “…will stop one of the runs, but not all of the runs.” (CDAP Lifecycle Microservices docs) Airflow already tracks a specific runId returned by DataFusionStartPipelineOperator (via XCom / returned value). Users need to stop that specific run deterministically, e.g. on DAG cancellation, failure cleanup, or manual stop workflows. CDAP provides a precise endpoint: `POST /v3/namespaces/<namespace-id>/apps/<app-id>/<program-type>/<program-id>/runs/<run-id>/stop` Airflow should support calling that endpoint when a runId is available. ### Related issues https://github.com/apache/airflow/pull/60688 ### Are you willing to submit a PR? - [ ] Yes I am willing to submit a PR! ### Code of Conduct - [x] I agree to follow this project's [Code of Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
