Re: [VOTE] New Airflow Community Provider: Teradata

This is good stuff! +1 non binding Thanks & Regards, Amogh Desai On Wed, Jan 17, 2024 at 9:31 AM Abhishek Bhakat wrote: > +1 non binding > > > On 17-Jan-2024, at 03:01, Aritra Basu wrote: > > > > +1 non binding > > > > -- > > Regards, > > Aritra Basu > > > > On Wed, Jan 17, 2024, 5:35 AM Wei

Re: [VOTE] New Airflow Community Provider: Teradata

+1 non binding > On 17-Jan-2024, at 03:01, Aritra Basu wrote: > > +1 non binding > > -- > Regards, > Aritra Basu > > On Wed, Jan 17, 2024, 5:35 AM Wei Lee wrote: > >> +1 non binding >> >> Best, >> Wei >> >>> On Jan 17, 2024, at 2:54 AM, Josh Fell >> wrote: >>> >>> +1 (binding) >>> >>> O

Re: [VOTE] New Airflow Community Provider: Teradata

+1 non binding -- Regards, Aritra Basu On Wed, Jan 17, 2024, 5:35 AM Wei Lee wrote: > +1 non binding > > Best, > Wei > > > On Jan 17, 2024, at 2:54 AM, Josh Fell > wrote: > > > > +1 (binding) > > > > On Tue, Jan 16, 2024 at 1:53 PM Vincent Beck > wrote: > > > >> +1 binding. Makes sense to me.

Re: [VOTE] New Airflow Community Provider: Teradata

+1 non binding Best, Wei > On Jan 17, 2024, at 2:54 AM, Josh Fell > wrote: > > +1 (binding) > > On Tue, Jan 16, 2024 at 1:53 PM Vincent Beck wrote: > >> +1 binding. Makes sense to me. >> >> On 2024/01/16 18:21:39 Jarek Potiuk wrote: >>> +1 binding >>> >>> On Tue, Jan 16, 2024 at 6:20 PM P

Re: [VOTE] Release Airflow 2.8.1 from 2.8.1rc1

+1 (binding): Checked all my changes, I ran airflow in a few combinations (MySQL / Postgres Local/Celery executor. It looks and works well - run a few dags and navigated through a number of screens. Checked licences, signatures, checksums, performed a "reproducible build" check and it worked (with

Re: [VOTE] New Airflow Community Provider: Teradata

+1 (binding) On Tue, Jan 16, 2024 at 1:53 PM Vincent Beck wrote: > +1 binding. Makes sense to me. > > On 2024/01/16 18:21:39 Jarek Potiuk wrote: > > +1 binding > > > > On Tue, Jan 16, 2024 at 6:20 PM Phani Kumar > > wrote: > > > > > +1 non binding > > > > > > On Tue, Jan 16, 2024 at 10:43 PM K

Re: [VOTE] New Airflow Community Provider: Teradata

+1 non binding On Tue, Jan 16, 2024 at 1:53 PM Vincent Beck wrote: > +1 binding. Makes sense to me. > > On 2024/01/16 18:21:39 Jarek Potiuk wrote: > > +1 binding > > > > On Tue, Jan 16, 2024 at 6:20 PM Phani Kumar > > wrote: > > > > > +1 non binding > > > > > > On Tue, Jan 16, 2024 at 10:43 PM

Re: [VOTE] New Airflow Community Provider: Teradata

+1 binding. Makes sense to me. On 2024/01/16 18:21:39 Jarek Potiuk wrote: > +1 binding > > On Tue, Jan 16, 2024 at 6:20 PM Phani Kumar > wrote: > > > +1 non binding > > > > On Tue, Jan 16, 2024 at 10:43 PM K Mallam, Sunil > > wrote: > > > > > Hello Airflow Community, > > > > > > Thank you very

Re: [VOTE] New Airflow Community Provider: Teradata

+1 binding On Tue, Jan 16, 2024 at 6:20 PM Phani Kumar wrote: > +1 non binding > > On Tue, Jan 16, 2024 at 10:43 PM K Mallam, Sunil > wrote: > > > Hello Airflow Community, > > > > Thank you very much for your comments/feedback on the Discussion Thread. > > > > I’m creating this voting thread fo

Re: [ANNOUNCE] New PMC member: Andrey Anshin (taragolis)

Congratulations, Andrey!! On 2024-01-16, 6:38 AM, "Josh Fell" mailto:josh.d.f...@astronomer.io.inva>LID> wrote: CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe. AVERTI

Re: [VOTE] New Airflow Community Provider: Teradata

+1 non binding On Tue, Jan 16, 2024 at 10:43 PM K Mallam, Sunil wrote: > Hello Airflow Community, > > Thank you very much for your comments/feedback on the Discussion Thread. > > I’m creating this voting thread for Teradata to be Airflow’s new community > provider. > > We have one 1 binding vote

[VOTE] New Airflow Community Provider: Teradata

Hello Airflow Community, Thank you very much for your comments/feedback on the Discussion Thread. I’m creating this voting thread for Teradata to be Airflow’s new community provider. We have one 1 binding vote from Kaxil and I request the other community members to share their votes. Below ar

Re: [EXTERNAL] Re: [Discuss] New Airflow Community Provider: Teradata

Great! Thank you, Josh. Sunil K Mallam Staff Product Manager – 3rd Party Developer Tools [A black and orange logo Description automatically generated] 17095 Via Del Campo Ct. San Diego, CA 92127 teradata.com This e-mail is from Teradata Corp

Re: [EXTERNAL] Re: [Discuss] New Airflow Community Provider: Teradata

Agree, On Tue, Jan 16, 2024 at 3:38 PM Josh Fell wrote: > Lots of great work here already. I say let's put it to a vote. > > On Tue, Jan 16, 2024 at 1:01 AM K Mallam, Sunil > wrote: > > > Hello Airflow Community, > > > > I just wanted to follow up on this thread before I start the voting > thre

Re: [EXTERNAL] Re: [Discuss] New Airflow Community Provider: Teradata

Lots of great work here already. I say let's put it to a vote. On Tue, Jan 16, 2024 at 1:01 AM K Mallam, Sunil wrote: > Hello Airflow Community, > > I just wanted to follow up on this thread before I start the voting thread. > > So far we’ve have 4 positive responses (with 1 binding vote). Is th

Re: [ANNOUNCE] New PMC member: Andrey Anshin (taragolis)

Congrats Andrey! Very well deserved indeed! On Mon, Jan 15, 2024 at 7:04 PM Wei Lee wrote: > Congrats Andrey! 🎉 > > Best, > Wei > > > On Jan 16, 2024, at 4:06 AM, Bishundeo, Rajeshwar > wrote: > > > > Congrats Andrey!! Well deserved!! > > > > -- Rajesh > > > > > > > > > > > > > > On 2024-01-15

Re: [DISCUSSION] Adding support for Qdrant provider

> self hosted image and the cloud offering, comprehensive integration tests with the Docker image should suffice. I am fine with that. On Tue, Jan 16, 2024 at 3:00 PM Anush Shetty wrote: > P.S. The updates to Qdrant and the clients are backwards compatible. > Further reducing any maintenance ov

Re: [DISCUSSION] Adding support for Qdrant provider

P.S. The updates to Qdrant and the clients are backwards compatible. Further reducing any maintenance overhead. On Tue, 16 Jan, 2024, 7:29 pm Anush Shetty, wrote: > We'd gladly add the integration tests along with the mock tests that are > currently in place and since there's no difference in ru

Re: [DISCUSSION] Adding support for Qdrant provider

We'd gladly add the integration tests along with the mock tests that are currently in place and since there's no difference in running a self hosted image and the cloud offering, comprehensive integration tests with the Docker image should suffice. As you said, would appreciate any thoughts from t

Re: [DISCUSSION] Adding support for Qdrant provider

BTW: Dashboard links here: https://airflow.apache.org/ecosystem/#airflow-provider-system-test-dashboards On Tue, Jan 16, 2024 at 2:39 PM Jarek Potiuk wrote: > I'd love to hear from others in the community who already use Qdrant what > they think :) ? > > Few comments to Anush: > > I did a bit of

Re: [DISCUSSION] Adding support for Qdrant provider

I'd love to hear from others in the community who already use Qdrant what they think :) ? Few comments to Anush: I did a bit of review of the links and did some usual research. 1) Re: requirements it does not introduce any big issues. Urllib3 < 2 is a bit strange (but we are anyhow limited by bo

Re: [LAZY CONSENSUS] Add Qdrant as a supported provider

The discussion thread: https://lists.apache.org/list.html?dev@airflow.apache.org On Tue, 16 Jan 2024 at 17:38, Anush Shetty wrote: > Hi Jarek. > Thanks for taking the time to take a look at this. > If you feel we can't have a [LAZY CONSENSUS] since there's a company > behind the Qdrant project,

[DISCUSSION] Adding support for Qdrant provider

Hello, Airflow community, I am Anush - an Integrations engineer at Qdrant. This discussion proposes to include Qdrant as a supported provider for Airflow. Following up on https://lists.apache.org/list.html?dev@airflow.apache.org. Qdrant - https://github.com/qdrant/qdrant, is an open-source vector

Re: [LAZY CONSENSUS] Add Qdrant as a supported provider

Hi Jarek. Thanks for taking the time to take a look at this. If you feel we can't have a [LAZY CONSENSUS] since there's a company behind the Qdrant project, that's completely fine. I'll open a discussion thread to follow this up. On Tue, 16 Jan 2024 at 17:24, Jarek Potiuk wrote: > -1 for now. >

Re: [LAZY CONSENSUS] Add Qdrant as a supported provider

-1 for now. I am not talking that I do not agree with having the provider, I just object to **just** start LAZY CONSENSUS without earlier discussion and explanation and justification why you think Qdrant is good for the community here and why it's not good to have Qdrant team to manage it on their

[VOTE] Release Airflow 2.8.1 from 2.8.1rc1

Hey fellow Airflowers, I have cut Airflow 2.8.1rc1. This email is calling a vote on the release, which will last at least 72 hours, from Tuesday, January 16, 2024 at 10:30 am UTC until Friday, January 19, 2024, at 10:30 am UTC