o-nikolas commented on issue #46787: URL: https://github.com/apache/airflow/issues/46787#issuecomment-2667404011
> My reasoning behind multiple pools: I can see them as semaphores and we may need them for different purposes other than only executor parallelism limitations. I think allowing tasks to run in multiple pools (which ever is free first in list order? randomly assigned? we'd have to figure that out) is also a very reasonable and cool request! I think it's related but not necessarily tightly coupled to marking which executors execute tasks from a given pool (which would solve your original issue). Both are very cool features! But likely work cannot get started soon as only Airflow 3.0 PRs are being reviewed/accepted into `main` at the moment. But I'd love to see these come along in Airflow >= 3.1 -- 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: commits-unsubscr...@airflow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
