Thanks TP for the rework.

I added some comments (iteration 2) on the migration ideas. I think these 
details make it clearer, still i have partial doubts how much burden we add to 
users to migrate DAGs to get to version 3. I very much favor the new templating 
but am not sure how many DAG authors we leave with migration problems behind.
Do we have a guess or estimation how much burden we as airflow developers need 
to keep as compatability compared to the amount of DAG templates that people 
neet to adjust?

Sent from Outlook for iOS<https://aka.ms/o0ukef>
________________________________
From: Tzu-ping Chung <t...@astronomer.io.INVALID>
Sent: Monday, July 29, 2024 8:54:58 PM
To: dev@airflow.apache.org <dev@airflow.apache.org>
Cc: michalmod...@google.com <michalmod...@google.com>
Subject: Re: [VOTE] AIP-80: Explicit Template Fields in Operator Arguments

I have updated the AIP to include the additional compatibility discussions in 
this thread. Please take a look again.

Specifically (although by no means exclusively) it would be awesome if Michał 
you could have a look and see if it addresses more of the concerns and could be 
viable for you. Although the vote is non-binding, I still would like to be more 
confident I tried to address the real concerns from the community, which is the 
real problem when it comes to migration.

Link to document for convenience 
https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcwiki.apache.org%2Fconfluence%2Fx%2F2grOEg&data=05%7C02%7CJens.Scheffler%40de.bosch.com%7C9318251bd2fe4490b64308dcafffffe5%7C0ae51e1907c84e4bbb6d648ee58410f4%7C0%7C0%7C638578761240102546%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=vVICot9p06VQJ56QmP9dwvEaWfpR7nCcMVqUexl6B3w%3D&reserved=0<https://cwiki.apache.org/confluence/x/2grOEg>

TP

Reply via email to