Re: [DISCUSS] Restore the SQL server backend

e are multiple sets of > artifacts for different forks of Airflow about which one to get. > > What are your thoughts on this? > > From: Jarek Potiuk > Date: Monday, June 3, 2024 at 9:32 PM > To: dev@airflow.apache.org > Cc: james.du...@improving.com.invalid > Subject: Re

Re: [DISCUSS] Restore the SQL server backend

Subject: Re: [DISCUSS] Restore the SQL server backend I am not sure if you read what I wrote with full understanding. To be perfectly honest - If you secure enough resources, I think *STILL* it will be better if you maintain your own fork and apply necessary changes and offer it commercially to

Re: [DISCUSS] Restore the SQL server backend

t 9:53 AM > To: dev@airflow.apache.org > Subject: Re: [DISCUSS] Restore the SQL server backend > The cost of maintaining it in Airflow repo (with CI/CI, GH issues etc) is, > unfortunately, just too much higher. > > On Thu, 13 Jun 2024 at 17:11, James Duong .invalid> > wrote

Re: [DISCUSS] Restore the SQL server backend

tiple sets of > artifacts for different forks of Airflow about which one to get. > > What are your thoughts on this? > > From: Jarek Potiuk > Date: Monday, June 3, 2024 at 9:32 PM > To: dev@airflow.apache.org > Cc: james.du...@improving.com.invalid > Subject: Re: [DISCUSS] R

Re: [DISCUSS] Restore the SQL server backend

on a plan that would provide the necessary involvement in the > community. > > Please allow me some time to see what is possible. > > From: Wei Lee > Date: Friday, May 31, 2024 at 8:45 AM > To: dev@airflow.apache.org > Cc: james.du...@improving.com.invalid > Subject: Re:

Re: [DISCUSS] Restore the SQL server backend

bject: Re: [DISCUSS] Restore the SQL server backend I agree with Jed and the following comments. If my memory serves me right, this topic has been discussed a few times in the past. 5% doesn't seem very convincing. Even if it's biased, I'm still not persuaded that there are a large

Re: [DISCUSS] Restore the SQL server backend

Damian Shaw < >> ds...@striketechnologies.com >>>> >>> wrote: >>> >>>> I would say that MSSQL was often marked as "experimental" ( >>>> >>> >> https://airflow.apache.org/docs/apache-airflow/2.6.0/howto/set-up-data

Re: [DISCUSS] Restore the SQL server backend

QL. > > > > We also understand and are ready to address the concerns stated in the > > vote about support and resolving CI issues. > > > > From: Jarek Potiuk > > Date: Thursday, May 30, 2024 at 3:47 PM > > To: dev@airflow.apache.org > > Subject: Re: [

Re: [DISCUSS] Restore the SQL server backend

2024 at 3:47 PM > To: dev@airflow.apache.org > Subject: Re: [DISCUSS] Restore the SQL server backend > Agree with all comments above. Also I think bringing MySQL back is going to > make it way more complex to implement some of the improvements we thought > about - mostly async DB operati

Re: [DISCUSS] Restore the SQL server backend

t; -Original Message- > From: Andrey Anshin > Sent: Thursday, May 30, 2024 2:39 PM > To: dev@airflow.apache.org > Cc: james.du...@improving.com.invalid > Subject: Re: [DISCUSS] Restore the SQL server backend > > There was a proposal to keep it in the past [1] with a short explanati

Re: [DISCUSS] Restore the SQL server backend

uot;. > > > > I think the more important fact is it was a real burden on development, > > and there was no MSSQL champion in the Airflow maintainers. > > > > -Original Message- > > From: Andrey Anshin > > Sent: Thursday, May 30, 2024 2:39 PM &

Re: [DISCUSS] Restore the SQL server backend

From: Andrey Anshin > Sent: Thursday, May 30, 2024 2:39 PM > To: dev@airflow.apache.org > Cc: james.du...@improving.com.invalid > Subject: Re: [DISCUSS] Restore the SQL server backend > > There was a proposal to keep it in the past [1] with a short explanation > why the maintainers did n

RE: [DISCUSS] Restore the SQL server backend

ion in the Airflow maintainers. -Original Message- From: Andrey Anshin Sent: Thursday, May 30, 2024 2:39 PM To: dev@airflow.apache.org Cc: james.du...@improving.com.invalid Subject: Re: [DISCUSS] Restore the SQL server backend There was a proposal to keep it in the past [1] with a short explan

Re: [DISCUSS] Restore the SQL server backend

There was a proposal to keep it in the past [1] with a short explanation why the maintainers did not want to keep it. > many Microsoft customers who are using Airflow Microsoft also supports and participates in the development of PostgreSQL, there is one Core Team member and couple of Major Cont

Re: [DISCUSS] Restore the SQL server backend

I share Jed feeling. The effort required to maintain those compare to the value it actually brings combined with the usage from the survey, it doesn’t seem worth it to me. On Thu 30 May 2024 at 19:16, Jed Cunningham wrote: > Just for context, here were (roughly) the results from the 2023 Airflow

Re: [DISCUSS] Restore the SQL server backend

Just for context, here were (roughly) the results from the 2023 Airflow survey: PostgreSQL: 75% MySQL: 15% MSSQL: 5% Also, there are already discussions about potentially dropping MySQL support in Airflow 3. Given all that and the points from the past vote, I don't think it makes much sense to br

[DISCUSS] Restore the SQL server backend

Hi Airflow community! The support for SQL has been removed starting Airflow version 2.9.0 and this is a concern for many Microsoft customers who are using Airflow. Many customers have a multi-cloud