You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@airflow.apache.org by "Ash Berlin-Taylor (JIRA)" <ji...@apache.org> on 2018/09/03 11:35:00 UTC

[jira] [Closed] (AIRFLOW-2784) Don't allow to create two CONNECTIONS with same name

     [ https://issues.apache.org/jira/browse/AIRFLOW-2784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ash Berlin-Taylor closed AIRFLOW-2784.
--------------------------------------
       Resolution: Invalid
    Fix Version/s:     (was: 1.10.1)
                       (was: 2.0.0)

This is by design - if you create two connections with the same conn_id then airflow will choose a random one each time it asks for that operator -- i.e. this is a method of load-balancing services.

> Don't allow to create two CONNECTIONS with same name
> ----------------------------------------------------
>
>                 Key: AIRFLOW-2784
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-2784
>             Project: Apache Airflow
>          Issue Type: Bug
>    Affects Versions: 1.10
>            Reporter: Some
>            Priority: Major
>
> Currently, airflow allow to create two CONNECTIONS with the same name (*conn id*).
> This is a bug since airflow doesn't know how to handle it.
> When creating a new connection there should be a check that the name is unique. If not unique raise an error in the UI.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)