You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Kaxil Naik (JIRA)" <ji...@apache.org> on 2018/09/17 00:23:00 UTC
[jira] [Updated] (AIRFLOW-1195) Cleared tasks in SubDagOperator do
not trigger Parent dag_runs
[ https://issues.apache.org/jira/browse/AIRFLOW-1195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kaxil Naik updated AIRFLOW-1195:
--------------------------------
Summary: Cleared tasks in SubDagOperator do not trigger Parent dag_runs (was: Cleared tasks in SubDagOperator do not trigger upstream dag_runs)
> Cleared tasks in SubDagOperator do not trigger Parent dag_runs
> --------------------------------------------------------------
>
> Key: AIRFLOW-1195
> URL: https://issues.apache.org/jira/browse/AIRFLOW-1195
> Project: Apache Airflow
> Issue Type: Bug
> Components: subdag
> Affects Versions: 1.8.1
> Reporter: Paul Zaczkieiwcz
> Assignee: Kaxil Naik
> Priority: Minor
> Attachments: example_subdag_operator.not-cleared.png, example_subdag_operator.section-2.cleared.png
>
>
> Let's say that you had a task fail in a SubDag. You fix the underlying issue and want Airflow to resume the DagRun where it left off. If this were a flat DAG, then all you need to do is clear the failed TaskInstance and its downstream dependencies. The GUI will happily clear all of them for you in a single PUT request! In order to resume a SubDag, you must clear the TaskInstance + downstream dependencies AND you must clear the SubDagOperator + downstream depencies WITHOUT clearing its recursive dependencies. There should be an option to recursively clear task instances in upstream SubDags.
> The attached files use the example_subdag_operator DAG to illustrate the problem. Before the screenshot, I ran the operator to completion, then cleared {{example_subdag_operator.section-2.section-2-task-5}}. Notice that {{example_subdag_operator.section-2}} is in the `running` state, but {{example_subdag_operator}} is still in the `success` state.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)