Re: [DISCUSS] Name for the Executor of AIP-69

2024-08-29 Thread Jens Scheffler
Full votes: +0.9 Distributed +0.5 External -0.5 Agent -1 Remote From: Scheffler Jens (XC-AS/EAE-ADA-T) Sent: Wednesday, August 28, 2024 2:06:20 PM To: dev@airflow.apache.org Subject: RE: [EXT] [DISCUSS] Name for the Executor of AIP-69 CAUTION: This email origina

Re: [DISCUSS] Name for the Executor of AIP-69

2024-08-28 Thread Oliveira, Niko
, August 28, 2024 2:06:20 PM To: dev@airflow.apache.org Subject: RE: [EXT] [DISCUSS] Name for the Executor of AIP-69 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. AVERTISSEMENT

Re: [DISCUSS] Name for the Executor of AIP-69

2024-08-28 Thread Scheffler Jens (XC-AS/EAE-ADA-T)
Ilile the additional ideas by Shubham, therefore I change my Voted a bit: * +1 for Remote * +0.9 for Edge - in my view this fits really very good (not the meaning like edge case or the browser named edge) because also some infrastructure providers call remote/sattelite data centers being

Re: [DISCUSS] Name for the Executor of AIP-69

2024-08-27 Thread Mehta, Shubham
om >„remote“/central site… > >Sent from Outlook for iOS<https://aka.ms/o0ukef> <https://aka.ms/o0ukef>;> >____________ >From: Jarek Potiuk mailto:ja...@potiuk.com>> >Sent: Tuesday, August 27, 2024 7:05:29 PM >To: dev@airflow.apache.org <

Re: [DISCUSS] Name for the Executor of AIP-69

2024-08-27 Thread Ash Berlin-Taylor
just do what the scheduler instructs to do. Controlled from >„remote“/central site… > >Sent from Outlook for iOS<https://aka.ms/o0ukef> >____ >From: Jarek Potiuk >Sent: Tuesday, August 27, 2024 7:05:29 PM >To: dev@airflow.apache.org >Su

Re: [DISCUSS] Name for the Executor of AIP-69

2024-08-27 Thread Bas Harenslak
__ > From: Jarek Potiuk mailto:ja...@potiuk.com>> > Sent: Tuesday, August 27, 2024 7:05:29 PM > To: dev@airflow.apache.org <mailto:dev@airflow.apache.org> > mailto:dev@airflow.apache.org>> > Subject: Re: [DISCUSS] Name for the Executor of AIP-69 >

Re: [DISCUSS] Name for the Executor of AIP-69

2024-08-27 Thread Scheffler Jens (XC-AS/EAE-ADA-T)
scheduler instructs to do. Controlled from „remote“/central site… Sent from Outlook for iOS<https://aka.ms/o0ukef> From: Jarek Potiuk Sent: Tuesday, August 27, 2024 7:05:29 PM To: dev@airflow.apache.org Subject: Re: [DISCUSS] Name for the Executor of AIP-69 ag

Re: [DISCUSS] Name for the Executor of AIP-69

2024-08-27 Thread Jarek Potiuk
nly in our docs but in our previous > >>> summit talks, town halls, Github Issues/Discussions, Slack threads, > etc. > >>> It's a term we've used as a community for years. So we should not > change > >>> all that under the feet of our users just because

Re: [DISCUSS] Name for the Executor of AIP-69

2024-08-27 Thread Ash Berlin-Taylor
t;>> new name for AIP-69. I think distributed is good for this new feature, but >>> I am also curious to see if anyone has other proposals. >>> >>> >>> From: Vincent Beck >>> Sent: Tuesday, August 27, 2024 7:53:27 AM &

Re: [DISCUSS] Name for the Executor of AIP-69

2024-08-27 Thread Daniel Standish
the feet of our users just because it is difficult to find a >> new name for AIP-69. I think distributed is good for this new feature, but >> I am also curious to see if anyone has other proposals. >> >> >> From: Vincent Beck >>

Re: [DISCUSS] Name for the Executor of AIP-69

2024-08-27 Thread Daniel Standish
t because it is difficult to find a > new name for AIP-69. I think distributed is good for this new feature, but > I am also curious to see if anyone has other proposals. > > > From: Vincent Beck > Sent: Tuesday, August 27, 2024 7:53:27 AM > To:

Re: [DISCUSS] Name for the Executor of AIP-69

2024-08-27 Thread Oliveira, Niko
3:27 AM To: dev@airflow.apache.org Subject: RE: [EXT] [DISCUSS] Name for the Executor of AIP-69 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. AVERTISSEMENT: Ce courrier électroniqu

Re: [DISCUSS] Name for the Executor of AIP-69

2024-08-27 Thread Vincent Beck
Distributed makes more sense to me. +1 binding on this one. Remote executor is too broad to me On 2024/08/27 14:43:33 Jarek Potiuk wrote: > I prefer distributed - as Remote executor is already a well-established > term. But this is -0.5 on "remote" - if others think it's ok, I am fine. > > On Tu

Re: [DISCUSS] Name for the Executor of AIP-69

2024-08-27 Thread Jarek Potiuk
I prefer distributed - as Remote executor is already a well-established term. But this is -0.5 on "remote" - if others think it's ok, I am fine. On Tue, Aug 27, 2024 at 3:33 PM Scheffler Jens (XC-AS/EAE-ADA-T) wrote: > Hi Airflow-Devs, > > AIP-69 has come as MVP to the front-door of the repo in

[DISCUSS] Name for the Executor of AIP-69

2024-08-27 Thread Scheffler Jens (XC-AS/EAE-ADA-T)
Hi Airflow-Devs, AIP-69 has come as MVP to the front-door of the repo in form of 3 PRs. But as in the Voting there has been a bit of discussion about how we call that "baby" I'd like to have a wrap-up about the name and see what the majority is for. The AIP-69 defined the implementation as "Rem