[
https://issues.apache.org/jira/browse/AIRFLOW-4139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chao-Han Tsai updated AIRFLOW-4139:
-----------------------------------
Description:
Currently, running DagRun will be impacted if we change the DAG file in the
middle of the run. After we have
https://cwiki.apache.org/confluence/display/AIRFLOW/AIP-5+Remote+DAG+Fetcher
and https://cwiki.apache.org/confluence/display/AIRFLOW/AIP-20+DAG+manifest
ready, we can start saving each version of the DAG file on the remote system
and the running tasks should refer to a specific version of DAG instead of the
latest DAG.
How is it different from
was:Currently, running DagRun will be impacted if we change the DAG file in
the middle of the run. After we have
> DAG versioning
> --------------
>
> Key: AIRFLOW-4139
> URL: https://issues.apache.org/jira/browse/AIRFLOW-4139
> Project: Apache Airflow
> Issue Type: New Feature
> Reporter: Chao-Han Tsai
> Assignee: Chao-Han Tsai
> Priority: Major
>
> Currently, running DagRun will be impacted if we change the DAG file in the
> middle of the run. After we have
> https://cwiki.apache.org/confluence/display/AIRFLOW/AIP-5+Remote+DAG+Fetcher
> and https://cwiki.apache.org/confluence/display/AIRFLOW/AIP-20+DAG+manifest
> ready, we can start saving each version of the DAG file on the remote system
> and the running tasks should refer to a specific version of DAG instead of
> the latest DAG.
> How is it different from
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
