potiuk commented on issue #14529: URL: https://github.com/apache/airflow/issues/14529#issuecomment-1132690441
I think you can definitely make a PR for it if you fill like it. There is a certain complexity of automating it which makes it complex - if you want to run it in single transaction (i.e. fast) you will start hitting the potential deadlock scenarios i mentioned. If you want to make it to 'simulate' users doing it one by one in each transaction separately, the you will have another problem - with even 10s of tasks such operation will tke potentially minutes - at which point you have to consider which entity is controlling the lopping and 'clicking'. Whe you are doing it manually - you are that entity and then you can manually react the situation where one of those actions fails, timeouts or is already outdated because state of the task changed. When you want to do it in 'fire and forget' mode you need to first of all handle all those cases and secondly - give a user feedback and chance to react and take different actions. All this has to be implemented. And there is a question where should it be controlled from - is it from the browser client (JavaScript) or some server job which is running a long running job looping over the tasks. Both have pros and cons. You are basically speaking about replacing a human cdoing multiple actions one by one and reacting differently to it with someltllthing that runs in the background and does the same and reacts to different errors. So i am not at all talking it's not possible. It certainly is. It's just much more complex than you think on the surface and someone has to simply ... Implement it taking into account all the complexity. If you think it is 'simple' then it probably means you can easily submit a PR for that. I am happy to revisew it actually and discuss all the scenarios during review that i explained above J. -- 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]
