potiuk commented on issue #31491: URL: https://github.com/apache/airflow/issues/31491#issuecomment-1592601588
I would be agains fixing it. I think the milk has spilled a long time ago and reverting the behaviour after it has been changed and released in 2.0, 2.1, 2.2, 2.3, 2.4, 2.5, 2.6 will bring more harm than good. If anything this bring more harm than good. I believe we already have good solution for that in task group https://github.com/apache/airflow/pull/26658 (available to 2.5) and if anything we should not fix it, but we should use it drive people who want to use it to switch to Task Group. > I know that subdag is deprecated. But for some reason, there are people like me who haven't converted to taskgroups yet. This is important to me. I would like you to review the bugfix. Yes. And - to be perfectly honest and brutal - by deprecating and providing the replacement, we want to drive them out of using subdag as soon as possible. So while not intentional, the result of this bug is that people like you are more likely to have incentive to switch to the Task Group. Also - look at it from the other perspective. You probably don't realise that we would only implement such change in main and release in 2.7 if we decide to do so, So maybe it will get relased in a few months and it will get few more weeks to get 2.7.1 tha will have some teething problems solved.. Then it will take few more months for composer to support that version - and only then you will have to migrate going through all the hoops of going 2.4 -> 2.7 and ony then you wil be able to use the fix, providing that it works. You are looking at maybe 6 months + migration between 3 versions of airlfow to use the fix you propose. Alternative - you migrate now to 2.5 and switch to Task Group. Thinks which way is more costly to your business. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
