Re: [DISCUSS] indexes for API calls

2024-06-17 Thread Jarek Potiuk
Yes. I agree. Airflow REST API does not have to be super efficient with the exception of designated calls which are really designed to be efficient. We might want to speed up some things for the Airflow Ui purposes for example. And it should always be explicit decision when we add new filtering etc

Re: Google Provider Package System Tests Dashboard

2024-06-17 Thread Ferruzzi, Dennis
It's great to see another big provider adding a system test dashboard! As Jarek mentioned, that's a nice majority of the system tests covered now. - ferruzzi From: Kaxil Naik Sent: Friday, June 14, 2024 3:14 AM To: dev@airflow.apache.org Subject: RE: [EXT]

Re: [DISCUSS] indexes for API calls

2024-06-17 Thread Daniel Standish
I tinkered with this a bit. I think the case to add indexes for "REST" API may be weaker than even *I* thought (and I thought it was weak / was mostly against it). The reason is cus there are reasons beyond indexing why such API calls are slow, and adding indexes may not even help that much. For

Re: [VOTE] Release Apache Airflow Helm Chart 1.14.0 based on 1.14.0rc1

2024-06-17 Thread Jed Cunningham
If you reimport from KEYS, I've already updated the expiration date a while back :).

Re: [LAZY CONSENSUS] Introduce common.compat provider

2024-06-17 Thread Maciej Obuchowski
I know it's a lazy consensus, but I want to explicitly +1 this :) pon., 17 cze 2024 o 11:15 Jarek Potiuk napisał(a): > Also the discussion was continued there > https://lists.apache.org/thread/hjmrv1wc2rxhkvozpvccs4mhgwg5sw2f (for > posterity) > > On Mon, Jun 17, 2024 at 11:06 AM Jarek Potiuk w

Re: [DISCUSS] Number of queries to Airflow database in "DAG File Processing Stats"

2024-06-17 Thread Eugen Kosteev
Thanks for your feedback! Someone from the Cloud Composer team will work on it ~this week. We will create an issue on https://github.com/apache/airflow/issues for this change. - Eugene On Fri, Jun 14, 2024 at 11:47 PM Daniel Standish wrote: > I wonder if we could generalize to summarize what n

Re: [LAZY CONSENSUS] Introduce common.compat provider

2024-06-17 Thread Jarek Potiuk
Also the discussion was continued there https://lists.apache.org/thread/hjmrv1wc2rxhkvozpvccs4mhgwg5sw2f (for posterity) On Mon, Jun 17, 2024 at 11:06 AM Jarek Potiuk wrote: > Hello everyone, > > Following the discussion > https://lists.apache.org/thread/r302p5b03dpyncswn11nkjn98cpb6r5z I would

[LAZY CONSENSUS] Introduce common.compat provider

2024-06-17 Thread Jarek Potiuk
Hello everyone, Following the discussion https://lists.apache.org/thread/r302p5b03dpyncswn11nkjn98cpb6r5z I would like to call for a lazy consensus on introdiucing "common.compat" provider. Summarizing what has been discussed there (and some of my further thoughts): * common.compat provider will

Re: [VOTE] Release Apache Airflow Helm Chart 1.14.0 based on 1.14.0rc1

2024-06-17 Thread Rahul Vats
+1 non binding Installed chart with kind cluster and verified running example dags. LGTM! Regards, Rahul Vats 9953794332 On Mon, 17 Jun 2024 at 13:19, Ephraim Anierobi wrote: > +1 binding > > Confirmed reproducibility, licenses, checksums, and signatures. It looks > good though Jed's signature

Re: [VOTE] Release Apache Airflow Helm Chart 1.14.0 based on 1.14.0rc1

2024-06-17 Thread Ephraim Anierobi
+1 binding Confirmed reproducibility, licenses, checksums, and signatures. It looks good though Jed's signature has expired but I don't think it's a problem Installed the chart and ran some example dags - Ephraim On Mon, 17 Jun 2024, 07:17 Amogh Desai, wrote: > +1 non binding > > Installed th