[
https://issues.apache.org/jira/browse/AIRFLOW-1383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gordon Ball updated AIRFLOW-1383:
---------------------------------
Description:
The CLI command {{airflow clear}} does not expose any way to set the
{{reset_dag_runs}} parameter of the underlying {{DAG.clear()}} method.
This means that {{airflow clear}} will always cause affected DAG runs to be set
to {{state=RUNNING}}, and immediately try and re-run the cleared tasks. In some
circumstances it might not be desirable to immediately re-run everything.
I would propose to add a new argument to {{airflow clear}} ({{no_dag_reset}}?)
which overrides the default.
was:
The CLI command {{airflow clear}} does not expose any way to set the
{{reset_dag_runs}} parameter of the underlying {{DAG.clear()}} method.
This means that `airflow clear` will always cause affected DAG runs to be set
to {{state=RUNNING}}, and immediately try and re-run the cleared tasks. In some
circumstances it might not be desirable to immediately re-run everything.
I would propose to add a new argument to {{airflow clear}} ({{no_dag_reset}}?)
which overrides the default.
> CLI clear command always resets DAG runs
> ----------------------------------------
>
> Key: AIRFLOW-1383
> URL: https://issues.apache.org/jira/browse/AIRFLOW-1383
> Project: Apache Airflow
> Issue Type: Improvement
> Components: cli
> Affects Versions: Airflow 1.8
> Reporter: Gordon Ball
> Priority: Minor
>
> The CLI command {{airflow clear}} does not expose any way to set the
> {{reset_dag_runs}} parameter of the underlying {{DAG.clear()}} method.
> This means that {{airflow clear}} will always cause affected DAG runs to be
> set to {{state=RUNNING}}, and immediately try and re-run the cleared tasks.
> In some circumstances it might not be desirable to immediately re-run
> everything.
> I would propose to add a new argument to {{airflow clear}}
> ({{no_dag_reset}}?) which overrides the default.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
