[Discuss] Airflow 2 to 3 migration rules

2024-08-21 Thread Wei Lee
Hey everyone, We are currently implementing some breaking changes to the main branch. I've created this issue to keep track of the items that need to be included in our migration tool from version 2 to 3. I've provided two examples and will add more in the upcoming days. It would be great if we co

Re: [Discussion] Add a new TriggerRule: Never

2024-08-21 Thread Oliveira, Niko
To me I think if we have a trigger rule of run always, then a rule of run never isn't so unreasonable. Also regarding just adding the code snippet inline in the docs, rather than importing from the DAG: The nice thing about having it come from the system test DAG is that the code snippet stays

Re: [VOTE] Airflow Providers prepared on August 19, 2024

2024-08-21 Thread Ash Berlin-Taylor
+1 binding > On 21 Aug 2024, at 05:44, Rahul Vats wrote: > > +1 non-binding. Verified below providers with our example DAGS > > 1. https://pypi.org/project/apache-airflow-providers-pgvector/1.3.0rc1/ > 2. https://pypi.org/project/apache-airflow-providers-pinecone/2.1.0rc1/ > 3. https://py

Re: [DISCUSS] Airflow 2.11 as bridge release

2024-08-21 Thread Oliveira, Niko
Agree with Elad's take on this. I'd say no "large" features, but leaving some wiggle room for changes that allow an easier segue to Airflow 3 would be great. From: Amogh Desai Sent: Tuesday, August 20, 2024 8:53:21 PM To: dev@airflow.apache.org Subject: RE: [EXT]

Re: [Discussion] Add a new TriggerRule: Never

2024-08-21 Thread Jarek Potiuk
> > > Also regarding just adding the code snippet inline in the docs, rather > than importing from the DAG: The nice thing about having it come from the > system test DAG is that the code snippet stays up to date. Even if the task > is being skipped, at least linters, static analysis, or failures d

Re: [DISCUSS] allow_trigger_in_future setting: keep or chop?

2024-08-21 Thread Oliveira, Niko
I don't feel too strongly about this one (I suppose I also lean allow) but I agree with removing as many of these configs as possible! So I'm all for this one, either way. From: Daniel Standish Sent: Thursday, August 15, 2024 6:13:31 PM To: dev@airflow.apache.or

Re: [VOTE] Airflow Providers prepared on August 19, 2024

2024-08-21 Thread Hussein Awala
+1 (binding) checked signatures, checksums, licences, and sources. On Wednesday, August 21, 2024, Ash Berlin-Taylor wrote: > +1 binding > > > On 21 Aug 2024, at 05:44, Rahul Vats wrote: > > > > +1 non-binding. Verified below providers with our example DAGS > > > > 1. https://pypi.org/project/

Re: [VOTE] New Provider for Core operators/sensor

2024-08-21 Thread Ferruzzi, Dennis
> +0.5 for essential/s - it gives me a sense that it is mandatory The essential/core/whatever-we-call-this will be an Airflow dependency and installed any time you install Airflow so that's pretty accurate. - ferruzzi From: Amogh Desai Sent: Tuesday, August 2

Re: [DISCUSS] allow_trigger_in_future setting: keep or chop?

2024-08-21 Thread Jarek Potiuk
weak allow as well. On Wed, Aug 21, 2024 at 8:31 PM Oliveira, Niko wrote: > I don't feel too strongly about this one (I suppose I also lean allow) but > I agree with removing as many of these configs as possible! So I'm all for > this one, either way. > > > From: