hterik opened a new issue, #35174:
URL: https://github.com/apache/airflow/issues/35174
### Description
Schedule tasks based on labels/capabilities with and+or matching, instead of
just queue names.
### Use case/motivation
Imagine you have tasks that can only run on speci
github-actions[bot] commented on issue #35174:
URL: https://github.com/apache/airflow/issues/35174#issuecomment-1804872625
This issue has been automatically marked as stale because it has been open
for 14 days with no response from the author. It will be closed in next 7 days
if no further
github-actions[bot] closed issue #35174: Node label/capability based scheduling
(for CeleryExecutor)
URL: https://github.com/apache/airflow/issues/35174
--
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
github-actions[bot] commented on issue #35174:
URL: https://github.com/apache/airflow/issues/35174#issuecomment-1815527746
This issue has been closed because it has not received response from the
issue author.
--
This is an automated message from the Apache Git Service.
To respond to the
jens-scheffler-bosch commented on issue #35174:
URL: https://github.com/apache/airflow/issues/35174#issuecomment-1781515443
Such feature is indirectly supported with a single "label" using the "queue"
feature. You can assign tasks to "queues" and workers can pull work from one or
multiple q
jens-scheffler-bosch commented on issue #35174:
URL: https://github.com/apache/airflow/issues/35174#issuecomment-1781601318
To map the current queue features to your demand, a workaround to implement
the demand you are raising your be:
* Node 1: Listen to queue `linux` and `x86`
*