Re: [DISCUSS] AIP-67 Multi-team deployment of Airflow components (reloaded)

2024-07-18 Thread Amogh Desai
Nice, thanks for clarifying all this! Now that I read the new proposal, it is adding up to me why certain decisions were made. The decision to separate the "common" part from the "per team" part adds up now. It is a traditional paradigm of separating "control plane" from "compute". Thanks & Regar

Re: [VOTE] (v2) AIP-69 Remote Executor

2024-07-18 Thread Oliveira, Niko
Overall I'm +1 NOTE: I still strongly believe we should _not_ brand this "Remote Executors" we already use Remote Executors (to mean CeleryExecutor, K8sExecutor, etc) in many many contexts as a contrast to Local Executors (LocalExecutor, SequentialExecutor). It's in our docs, blog posts, Airflo

Re: Operator Templating in Airflow 3

2024-07-18 Thread Vincent Beck
+1 here as well. Keeping these template_fields in sync with the parameters has always been a challenge. Happy to no longer check that when doing PR reviews. On 2024/07/18 20:14:13 "Scheffler Jens (XC-AS/EAE-ADA-T)" wrote: > Bis +1 from me. The existing Jinja Syntax was a pitfall for all firdt tim

Re: Operator Templating in Airflow 3

2024-07-18 Thread Scheffler Jens (XC-AS/EAE-ADA-T)
Bis +1 from me. The existing Jinja Syntax was a pitfall for all firdt time DAG developers and there are many hard-to-read examples neede for medium conplex things like a dict with templated fields some comments left in the doc. Looking forward for an AIP Sent from Outlook for iOS

Re: [DISCUSS] To AIP-44 or not to AIP-44

2024-07-18 Thread Jarek Potiuk
Remote Executor not worker. On Thu, Jul 18, 2024 at 8:52 PM Jarek Potiuk wrote: > My conclusion is (I spoke to Jens about it today) that we should attempt > to get a "workable, not necessarily optimized for performance, and > potentially having a few things not working version of it" and label i

Re: [DISCUSS] To AIP-44 or not to AIP-44

2024-07-18 Thread Jarek Potiuk
My conclusion is (I spoke to Jens about it today) that we should attempt to get a "workable, not necessarily optimized for performance, and potentially having a few things not working version of it" and label it " highly experimental, don't do it at home" - rather similar to what Jens' approach is

[ANNOUNCE] Airflow Summit 2024 - Program is ready

2024-07-18 Thread Teyza Ponce
[image: Airflow Summit 2024] *Exciting news!* The program for Airflow Summit 2024 is now ready. Explore the featured sessions and full program . Save your spot to celebrate the 10th anniversary of Apache Airflow. Don’t forget to book

Re: [DISCUSS] To AIP-44 or not to AIP-44

2024-07-18 Thread Daniel Standish
I don't have strong feelings here either way, but we should probably try to arrive at a conclusion here sooner than later because meanwhile work on this continues. I think the question is sort of, is anyone going to essentially veto it, or perhaps veto it unless certain conditions are met. E.g. i