+1
> On 24 Apr 2020, at 13:28, Jarek Potiuk <jarek.pot...@polidea.com> wrote:
>
> +1
>
> On Fri, Apr 24, 2020 at 12:31 PM Ash Berlin-Taylor <a...@apache.org> wrote:
>
>> As we discussed in the thread on Spec thread for our new API, the idea
>> came up of making conn_id unique in Airflow
>>
>> <
>> https://lists.apache.org/thread.html/rfb6f7d95b2754fda9dd09b08444214dfad12d10f143d32de0fcf4104%40%3Cdev.airflow.apache.org%3E
>>>
>>
>> The people in that thread seemed to be in favour of it:
>>
>> - It is often confusing to users (there have been a few bug reports
>> about it over the years)
>> - It's questionable if it actually works well or not
>> - There are better/smarter tools for loadbalancing connections to a DB
>> than picking one of a random list
>> - For Hive at least it has been implemented another way - allowing two
>> host's in a single connection string
>> https://github.com/apache/airflow/pull/4708 (available in 1.10.6)
>> - It makes the HTTP API confusing (needing a integer connection ID, and
>> a string conn_id field)
>>
>> Given the downsides/work arounds, and the confusion this causes to I
>> propose we remove this (mis)feature from Airflow 2.0.
>>
>> Kevin from AirBnb (on bcc, hopefully you see this) I would be interested
>> in your vote/view, as I know AirBnB was using this in the past.
>>
>> This vote will last for 96 Hours, until 10:30Z on 2020-04-27
>> https://www.timeanddate.com/worldclock/fixedtime.html?iso=20200427T1030
>>
>> Every vote counts here, so please all vote.
>>
>> Options:
>>
>>
>> [ ] +1 approve
>> [ ] +0 no opinion
>> [ ] -1 disapprove with the reason
>>
>> (or fractional values between -1..+1)
>>
>> This is my +1 vote.
>>
>> Thanks,
>> Ash
>>
>
>
> --
>
> Jarek Potiuk
> Polidea <https://www.polidea.com/> | Principal Software Engineer
>
> M: +48 660 796 129 <+48660796129>
> [image: Polidea] <https://www.polidea.com/>
