GitHub user yuqian90 added a comment to the discussion: Clarification on
ExternalTaskMarker Behavior and Recursive Clearing in Airflow 3.0
It seems the UI in Airflow 3.0 no longer supports clearing Past, Future,
Downstream or Recursive. It looks like an oversight. Fixing it probably
requires some UI changes and in the corresponding openapi function. As seen
here the api call doesn't even consider arguments such as Past, Future,
Downstream or Recursive.
I wonder if anyone else is encountering this problem?
```
/**
* Get Mapped Task Instance
* Get task instance.
* @param data The data for the request.
* @param data.dagId
* @param data.dagRunId
* @param data.taskId
* @param data.mapIndex
* @returns TaskInstanceResponse Successful Response
* @throws ApiError
*/
public static getMappedTaskInstance(
data: GetMappedTaskInstanceData,
): CancelablePromise<GetMappedTaskInstanceResponse> {
return __request(OpenAPI, {
method: "GET",
url:
"/api/v2/dags/{dag_id}/dagRuns/{dag_run_id}/taskInstances/{task_id}/{map_index}",
path: {
dag_id: data.dagId,
dag_run_id: data.dagRunId,
task_id: data.taskId,
map_index: data.mapIndex,
},
errors: {
401: "Unauthorized",
403: "Forbidden",
404: "Not Found",
422: "Validation Error",
},
});
}
```
GitHub link:
https://github.com/apache/airflow/discussions/46385#discussioncomment-13228498
----
This is an automatically sent email for [email protected].
To unsubscribe, please send an email to: [email protected]
