Roster created AIRFLOW-4955:
-------------------------------
Summary: Enforce Connections & Pools
Key: AIRFLOW-4955
URL: https://issues.apache.org/jira/browse/AIRFLOW-4955
Project: Apache Airflow
Issue Type: Wish
Components: core
Affects Versions: 2.0.0
Reporter: Roster
Airflow allows Polls and Connection yet the integration between them is up to
the user.
We have 40+ users who upload DAGs. It's impossible to manully enforce that if
user choose to use Connection "X_y_Z" then he must also use Pool "X_Y_Z_P".
We would love a feature where in the Connection you can associate it to a Pool.
So whenever the user is specifying this connection in Operator/Hook he must
also specify the Pool - Otherwise the Operator will fail!
Or even better save the trouble of having the users to manually specify the
pool in the Operator - and stack up the tasks in the pool by itself.
I'm not asking to change the current behavior of Pools. This can be an
extension of the current behavior. Think of it like queues... The user who
writing operator doesn't need to specify to which worker queue the tasks will
go. Airflow handle it for him. then why not with Connections and Pools?
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
