kaxil opened a new issue, #76778:
URL: https://github.com/apache/airflow/issues/76778
In Airflow 2, clearing a whole Dag run also cleared the tasks its
`ExternalTaskMarker`s point at, and their downstream tasks, in the other Dags.
The UI's Dag run clear called `dag.clear(..., include_subdags=True)` and the
REST API's `POST /dags/{dag_id}/dagRuns/{dag_run_id}/clear` did the same, and
`include_subdags` turned on the marker cascade.
#75874 brings the cascade back for task instance clears (`POST
/dags/{dag_id}/clearTaskInstances` and the task instance clear dialogs) only.
Clearing a Dag run from the UI or through `POST
/api/v2/dags/{dag_id}/dagRuns/{dag_run_id}/clear` still stays inside the one
Dag.
The Dag run clear route could reuse `find_dependent_clears` and
`clear_dependent_runs` from the task instance clear route, with the same
`include_dependent_dags` field and the same permission check per target Dag.
--
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]
