potiuk commented on PR #44494: URL: https://github.com/apache/airflow/pull/44494#issuecomment-2509010130
> While I accept it is temporarily broken in Airflow 3 (Still running behind trying to make EdgeExecutor working on main (again after the stone was hitting the glass) with the ongoing changes and merges to EdgeExecutor it is also throwing stones on the ability to further use it in Airflow 2.10. I think we should not hold back the changes for Airflow 2.10 compatibilty. This is the main think we discussed before that it will have to end at some point of time - when it starts blocking our Airflow 3 development, And I think this is the time. I'd say - if we need to have new features of `edge executor` to work for 2.10 (particularly in your installation - I doubt it is used by anyone else) then maybe you should fork airflow right before we started to remove AIP-44 stuff, and continue to work on changes in standard executor that will be `2.10` compatible there - and build it and use it internally. I think that was inevitable and there is no better way - there is no easy way same edge executor will work for both 2.10 and 3 becasue the APIs will be so vastly different (and missing in Airflow 3). I'd say that this is the right moment to break the compatibility and let the burden on maintaining 2.10 variant of the edge executor to stay in the hands of Bosh, rather than keep us from cleaning and developing Airflow 3. @kaxil @ashb - I guess the AIP-44 code is keeping you from AIP-72 progressing (it looked like from the discussions we had so far and the plans for next week to make PRs that are overlapping with the current AIP-44 cleanup. We can raise it as a discussion at the devlist as well, but I think that was part of the agreement that we keep AIP-44 and Edge Executor happy with it for as long as we can - and I think "as long as we can" is "NOW". -- 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]
