[
https://issues.apache.org/jira/browse/AIRFLOW-4139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16799264#comment-16799264
]
Chao-Han Tsai commented on AIRFLOW-4139:
----------------------------------------
I took a quick scan of
https://cwiki.apache.org/confluence/display/AIRFLOW/AIP-12+Persist+DAG+into+DB
and I think that they are only persisting DAG graphs for each DAG version in
the metastore just for the purpose of making webserver stateless. That is not
enough information to run a task at a given DAG version. We will need to
version the code in a way that Airflow worker can refer to.
What I am proposing here is that once 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 will have the DAG file stored in a versioned storage. Each running
TaskInstance would run specific version of code.
> 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.
> Existing running DagRun should not be impacted.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
