You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Jarek Potiuk (Jira)" <ji...@apache.org> on 2019/12/29 14:18:00 UTC
[jira] [Updated] (AIRFLOW-6390) DAG migration tool to 2.0.0
[ https://issues.apache.org/jira/browse/AIRFLOW-6390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jarek Potiuk updated AIRFLOW-6390:
----------------------------------
Description:
Before releasing 2.0.0, we should create DAG migration tool for migrating DAGs to Apache Airflow 2.0 based on UPDATING.md and incompatibilities introduced in 2.0.0
It should mostly automate migrating DAGs and correcting the DAGs they have where needed and print warnings for all cases that need some manual review and corrections (with appropriate instructions).
All the changes performed automatically should be explained and described and logged so that you can refer to changes made to your DAG.
The instructions in case of manual corrections needed should be more detailed than just describing the changes in UPDATING.md. It should mention consequences of such changes, reasoning and explain what the user might expect after migration.
We also will need the support of a number of "friendly" users with that.
We will provide some basic migration tool initially but it will take quite a few iterations to perfect it and handle all edge cases that we have not thought about. So we will need to release some beta-versions to test the tool on real-live DAGs by our users and handle those cases.
was:
Before releasing 2.0.0, we should create DAG migration tool for migrating DAGs to Apache Airflow 2.0 based on UPDATING.md and incompatibilities introduced in 2.0.0
It should mostly automate migrating DAGs and correcting the DAGs they have where needed and print warnings for all cases that need some manual review and corrections (with appropriate instructions).
All the changes performed automatically should be explained and described and logged so that you can refer to changes made to your DAG.
The instructions in case of manual corrections needed should be more detailed than just describing the changes in UPDATING.md. It should mention consequences of such changes, reasoning and explain what the user might expect after migration.
> DAG migration tool to 2.0.0
> ---------------------------
>
> Key: AIRFLOW-6390
> URL: https://issues.apache.org/jira/browse/AIRFLOW-6390
> Project: Apache Airflow
> Issue Type: New Feature
> Components: core
> Affects Versions: 1.10.2, 1.10.3, 1.10.4, 1.10.5, 1.10.6, 1.10.7
> Reporter: Jarek Potiuk
> Assignee: Jarek Potiuk
> Priority: Major
> Fix For: 2.0.0
>
>
> Before releasing 2.0.0, we should create DAG migration tool for migrating DAGs to Apache Airflow 2.0 based on UPDATING.md and incompatibilities introduced in 2.0.0
>
> It should mostly automate migrating DAGs and correcting the DAGs they have where needed and print warnings for all cases that need some manual review and corrections (with appropriate instructions).
> All the changes performed automatically should be explained and described and logged so that you can refer to changes made to your DAG.
> The instructions in case of manual corrections needed should be more detailed than just describing the changes in UPDATING.md. It should mention consequences of such changes, reasoning and explain what the user might expect after migration.
>
> We also will need the support of a number of "friendly" users with that.
>
> We will provide some basic migration tool initially but it will take quite a few iterations to perfect it and handle all edge cases that we have not thought about. So we will need to release some beta-versions to test the tool on real-live DAGs by our users and handle those cases.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)