potiuk commented on issue #32107:
URL: https://github.com/apache/airflow/issues/32107#issuecomment-1610789763

   Simple answer is "won't fix".  You should upgrade your Airflow because you 
are using version that stopped receiving any fixes 3 years ago - you are using 
extremely old, outdated, likely insecure version of software that is never 
going to receive any fix. Upgrade to Airflow 2 as soon as you possibly can, you 
are shooting yourself in the foot by using software that has reached EOL 
(end-of-life) 3 years ago.
   
   While I understand your request, this is a wrong forum to raise it. 
composer-1.20.12-1.10.15. is based on Airflow 1.10.15 that is end of life for 
almost 3 years now (which means that it stopped receiving any fixes - even 
including Critical security fixes 3 years ago. Since then there were more than  
10.000 chnages in Airlfow 2 - including thousands of bugfixes. And none of the 
changes, bugfixes will ever be applied to 1.10.15 - we stopped adding any fixes 
to 1.10 3 years ago. 
   
   If you look 
https://airflow.apache.org/docs/apache-airflow-providers-google/stable/index.html#changelog
 - there were ~30 reeleases or so of  just google provider that is used in 
Airflow 2 to communicate with Dataflow.
   
   This has been clearly communicated about 4.5 years ago and user had 1.5 year 
time to prepare back then. Since then - if somoene wants to keep 1.10.15 
running, they have to maintain it themselves. For example if Composer team 
released 1.10 they had longer maintenance window - and they would be 
responsible for adding any fixes, not the community here. Airlfow is 
open-source and anyone can apply their own patches.
   
   But I believe this has ended long time ago as well for any changes. You 
might check with Composer (unlike free, volunteer, as-people-have-time support 
- there you likely have paid support), but they likely do not support any 
changes or fixes other than critical ones for 1.10. I would be heavily 
surprised if they do.
   
   Airflow community we will **never** provide any fix any more according to 
this policy (even if there is a super critical security issue). It means 
"never" literally. In fact there maybe few people in the community that even 
remember what Airflow 1.10 was and wer around when it was released.
   
   Your best bet is to upgrade to some of the latest (maybe even latesst 
available version of Airflow.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to