potiuk commented on pull request #19592: URL: https://github.com/apache/airflow/pull/19592#issuecomment-1021032886
> @potiuk Upgrading will be an issue as it involves a long wait time. Have come up with the below 2 approaches as a fix for the time being. Sure you can come up with your own solutions if "not upgrading to a released patchlevel that contains a fix" is your own choice. But please don't ask maintainers to come up with workarounds if they already provided a fix that you can easily install. There is no way maintainers can give you another answer here - asking for it is quite unreasonable, because - the fix is there. What happens if (say) tomorrow we release 2.3.4 with a critical security fix (like Log4j) ? Would you take the risk of scrambling and trying to upgrade everything under the pressure of not only your security team but also your boss who will insist on fixing it "now". By not upgrading to latest released patchlevel, especially when it contains a fix to a known problem you have and opting to choose a workaround instead, you make yourself vulnerable to this scenario. But do not ask maintainers to either help you with it or endorse it, because we woudl be shooting ourselves in a foot (and your foot) by suggesting it. Of course, you are free to do what you want - we cannot stop you. But you've been warned. BTW. No 2.2.3 does not have any long migrations comparing to 2.2.2: https://airflow.apache.org/docs/apache-airflow/stable/migrations-ref.html?highlight=migrations it just adds one column to one table which should be almost instantenous. I'd really, really recommend you to upgrade. -- 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]
