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 2020/01/10 14:50:00 UTC

[jira] [Commented] (AIRFLOW-6524) Make trigger_dag & clear CLIs throw an error if 'shape' of dag has changed since prior dagrun

    [ https://issues.apache.org/jira/browse/AIRFLOW-6524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17012936#comment-17012936 ] 

Ash Berlin-Taylor commented on AIRFLOW-6524:
--------------------------------------------

They shouldn't fail -- once the state is running again does the "verify_integrity" call not create the missing tasks and set some to Removed?

> Make trigger_dag & clear CLIs throw an error if 'shape' of dag has changed since prior dagrun
> ---------------------------------------------------------------------------------------------
>
>                 Key: AIRFLOW-6524
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-6524
>             Project: Apache Airflow
>          Issue Type: Improvement
>          Components: cli, scheduler
>    Affects Versions: 1.10.7
>            Reporter: t oo
>            Priority: Trivial
>
> if DagA had 20 tasks on first exec_date but then DagA code was changed and had a different 15 or 25 tasks on second exec_date the scheduler will never run it. The CLI's for trigger_dag & clear should throw error right away to make it clear early that the Dagrun will never succeed.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)