You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@airflow.apache.org by "Ash Berlin-Taylor (JIRA)" <ji...@apache.org> on 2019/04/23 09:39:00 UTC

[jira] [Closed] (AIRFLOW-4389) trigger_dag cli 'force' option

     [ https://issues.apache.org/jira/browse/AIRFLOW-4389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ash Berlin-Taylor closed AIRFLOW-4389.
--------------------------------------
    Resolution: Won't Fix

If the dag already exists then clearing should be enough, and you don't need to re-trigger it as clearing the tasks will make them be picked up for scheduling.

(Also I don't know for certain but it sounds like that is somewhat counter to Airflow's design if you are clearing and re-running the same Dag Run instead of creating a new dag run)

> trigger_dag cli 'force' option
> ------------------------------
>
>                 Key: AIRFLOW-4389
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-4389
>             Project: Apache Airflow
>          Issue Type: New Feature
>          Components: cli
>    Affects Versions: 1.10.3
>            Reporter: t oo
>            Priority: Minor
>
> I have a requirement to always run dags from the very start. Ideally there would be a trigger_dag force option that disregards all previous task states of the dag/execdate but instead I need to do:
>  # check dag state
>  ## if none then trigger_dag
>  ## else clear



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)