[VOTE] (v2) AIP-69 Remote Executor

2024-07-16 Thread Scheffler Jens (XC-AS/EAE-ADA-T)
Hi Developers, After some further discussion time I’d like to call for a vote for AIP-69. All details are described in: https://cwiki.apache.org/confluence/display/AIRFLOW/AIP-69+Remote+Executor Note: * Compared to first VOTE in https://lists.apache.org/thread/tyfsrpjn12sz9dw50pbg16dsv6lmj

Re: [Meeting Notes] Airflow 3.0 Dev call - 11 July 2024

2024-07-16 Thread Vikram Koka
Thanks for the meeting notes Kaxil, this looks right. One key takeaway from the meeting was the relationship between AIP-38, AIP-68, and now AIP-79. The sooner we can clarify the dependencies here and establish the fallbacks i.e. with respect to FAB auth, the better from a risk management perspect

[Meeting Notes] Airflow 3.0 Dev call - 11 July 2024

2024-07-16 Thread Kaxil Naik
Hey all, I have updated our meeting notes document to summarize the discussion from our 11th July dev call for Airflow 3.0. Link: https://cwiki.apache.org/confluence/x/8ApeEg#Airflow3Devcall:MeetingNotes-11July2024 To all those who attended, can you please double-check and add if I have missed a

Re: [DISCUSS] AIP-66: DAG Bundles & Parsing

2024-07-16 Thread Jarek Potiuk
It looks very good now :) ! Yeah. The "execution environment" has many, many traps and edge cases. On Tue, Jul 16, 2024 at 10:19 PM Jed Cunningham wrote: > I've removed my attempt to bring python dependencies under versioning. The > scope is now DAG code and parsing control - still very useful,

Re: [DISCUSS] AIP-66: DAG Bundles & Parsing

2024-07-16 Thread Jed Cunningham
I've removed my attempt to bring python dependencies under versioning. The scope is now DAG code and parsing control - still very useful, 3.0 specific, and hopefully a bit less controversial.

Re: [RESULT] Accepted - AIP-72: Task Execution Interface aka Task SDK

2024-07-16 Thread Vikram Koka
Thank you all. I believe that this is an important foundational improvement for Airflow and really appreciate your support in moving this forward. Vikram On Tue, Jul 16, 2024 at 7:34 AM Ash Berlin-Taylor wrote: > This vote has passed with 13 binding +1s and five non-binding votes. > > Thanks a

Re: [ANNOUNCE] New committers: Rom Sharon & Shahar Epstein

2024-07-16 Thread Pierre Jeambrun
Congrats! On Tue 16 Jul 2024 at 09:04, Scheffler Jens (XC-AS/EAE-ADA-T) wrote: > Welcome Rom and Shahar! > > Mit freundlichen Grüßen / Best regards > > Jens Scheffler > > Alliance: Enabler - Tech Lead (XC-AS/EAE-ADA-T) > Robert Bosch GmbH | Hessbruehlstraße 21 | 70565 Stuttgart-Vaihingen | > GER

[RESULT] Accepted - AIP-72: Task Execution Interface aka Task SDK

2024-07-16 Thread Ash Berlin-Taylor
This vote has passed with 13 binding +1s and five non-binding votes. Thanks all. > On 15 Jul 2024, at 19:24, Amogh Desai wrote: > > +1 binding > > This AIP will finally attempt to solve some of the tough scaling challenges > and despite the fact that it will break a few things here and there,

Scheduler "workstream"? was: [DISCUSS] AIP-78 scheduler-managed backfill

2024-07-16 Thread Jarek Potiuk
Let me separate it to a different thread because yes - you are right Daniel - it should not be only AIP-78. > As I see it, minischeduler is unrelated and not what this AIP is about, and > basically does not matter for this AIP. And the broader discussion about > locking, while interesting, is al

[ANNOUNCE] Apache Airflow 2.9.3 Released

2024-07-16 Thread Utkarsh Sharma
Dear Airflow community, I'm happy to announce that Airflow 2.9.3 was just released. The released sources and packages can be downloaded via https://airflow.apache.org/docs/apache-airflow/stable/installation/installing-from-sources.html Other installation methods are described in https://airflow.

Re: Operator Templating in Airflow 3

2024-07-16 Thread Jarek Potiuk
I am all for the change - it's been a source of confusion. And yes, automatically rewriting the DAGs and possibly even detection with error explaining what to do (on Airflow 3) if template string is passed to "old" template_field - are really a prerequisite for that (and should be quite possible a

Re: Operator Templating in Airflow 3

2024-07-16 Thread Ephraim Anierobi
Good proposal. Big +1. I once had trouble with the trailing space issue and spent hours debugging it. Provided the migration tool can rewrite the DAGs, I support it. On Tue, 16 Jul 2024 at 08:42, Tzu-ping Chung wrote: > Good idea. Personally I think changing the import might be easier to read,

Re: Operator Templating in Airflow 3

2024-07-16 Thread Tzu-ping Chung
Good idea. Personally I think changing the import might be easier to read, but having a DAG policy is better if the goal is to rewrite DAG files as little as possible. Not sure if that’s a goal I’d agree with, but that’s not my decision to make 😛 I’ll find a way to add it to the document. >

Re: Operator Templating in Airflow 3

2024-07-16 Thread Tzu-ping Chung
> On Jul 16, 2024, at 14:38, Bas Harenslak wrote: > > +1 for this change! I especially had lots of trouble with template files with > templated filenames and this would solve it. > > Few comments/questions: > "improved debuggability when things go wrong": Could you elaborate on how > this pro

Re: Operator Templating in Airflow 3

2024-07-16 Thread Abhishek Bhakat
Seems nice. For the 2nd proposed change, I'm thinking another method for compat may be a dag_policy that drop-in replaces the params of any Operator. Avi

RE: [ANNOUNCE] New committers: Rom Sharon & Shahar Epstein

2024-07-16 Thread Scheffler Jens (XC-AS/EAE-ADA-T)
Welcome Rom and Shahar! Mit freundlichen Grüßen / Best regards Jens Scheffler Alliance: Enabler - Tech Lead (XC-AS/EAE-ADA-T) Robert Bosch GmbH | Hessbruehlstraße 21 | 70565 Stuttgart-Vaihingen | GERMANY | www.bosch.com Tel. +49 711 811-91508 | Mobil +49 160 90417410 | jens.scheff...@de.bosch.c