Yes definitely, I had thought of something like py2to3 script. We might want to create something similar.
On Sun, Dec 29, 2019, 14:17 Jarek Potiuk <[email protected]> wrote: > Great Claudio! Once we get closer to starting it, we can start some joined > work on it :). > > I think we also will need the support of a number of "friendly" users with > that. > > We can 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. > > J. > > > On Sun, Dec 29, 2019 at 3:09 PM Claudio <[email protected]> > wrote: > > > +1 Totally agree.Really would to work on this tool!Have a nice > day!Claudio > > -------- Messaggio originale --------Da: Jarek Potiuk < > > [email protected]> Data: 29/12/19 13:27 (GMT+01:00) A: > > [email protected] Oggetto: [PROPOSAL] [FUTURE] Semi-automated tool > > for migration to 2.0.0 I thought (and discussed with the users at various > > conferences) that weshould make it super-easy to migrate to Airflow 2.0 > > when we release it.There is a number of incompatibilities that we mention > > in UPDATING.md so wehave quite a good 'base' for the list of > > incompatibilities but I thinkpeople have 100s or 1000s of DAGs sometimes > so > > we should do better thanthat and provide a semi-automated migration tool > > for them.I'd love to hear what you think about it.I created a JIRA issue > > for it:https://issues.apache.org/jira/browse/AIRFLOW-6390Here is what it > > says:Before releasing 2.0.0, we should create DAG migration tool for > > migratingDAGs to Apache Airflow 2.0 based on UPDATING.md and > > incompatibilitiesintroduced in 2.0.0It should mostly automate migrating > > DAGs and correcting the DAGs they havewhere needed and print warnings for > > all cases that need some manual reviewand corrections (with appropriate > > instructions).All the changes performed automatically should be explained > > and describedand logged so that you can refer to changes made to your > > DAG.The instructions in case of manual corrections needed should be > > moredetailed than just describing the changes in UPDATING.md. It should > > mentionconsequences of such changes, reasoning and explain what the user > > mightexpect after migration.J.-- Jarek PotiukPolidea < > > https://www.polidea.com/> | Principal Software EngineerM: +48 660 796 > 129 > > <+48660796129>[image: Polidea] <https://www.polidea.com/> > > > > -- > > Jarek Potiuk > Polidea <https://www.polidea.com/> | Principal Software Engineer > > M: +48 660 796 129 <+48660796129> > [image: Polidea] <https://www.polidea.com/> >
