[
https://issues.apache.org/jira/browse/AIRFLOW-4139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16799271#comment-16799271
]
Tao Feng commented on AIRFLOW-4139:
-----------------------------------
there is a long pr([https://github.com/apache/airflow/pull/4396)] from the
user. I believe the graph_id is the version proposed by the AIP which the main
goal to solve the dag shape change problem. I would suggest you follow up with
author or mailing list to avoid any duplicate effort.
> 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
> https://cwiki.apache.org/confluence/display/AIRFLOW/AIP-12+Persist+DAG+into+DB?
> Please see
> https://issues.apache.org/jira/browse/AIRFLOW-4139?focusedCommentId=16799264&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16799264
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
