potiuk commented on issue #34748: URL: https://github.com/apache/airflow/issues/34748#issuecomment-1763465728
> Although version 2.7.8 is for GCP, but it is still very old. The requirements in the repo mention unsupported versions (2.4.1 / 1.0.0) . The versions need an update either way to keep up with the versions supported by Snowflake. > Maybe @potiuk have different view on this? I think I agree with you @eladkal that we should be careful, but also I think bumping to 2.7.8 should be quite fine here. Those two are not conflicting IMHO in this case. Currently the "golden" set of constraints we have - 3.2.1 / 1.5.0, so it will be generally "no-op" to bump the min versions to any higher version lower than that (from the maintenance point of view). For many smaller providers, we can just use very "recent" versions as min versions. When those providers have very few dependencies on their own. But Snowflake provider is different - the connector has 21 dependencies - many of them limited and many of them shared with other libraries. So bumping min version **might** cause the potential conflicts that @eladkal described (it already has in the past). One note worth mentioning though. We should be just a "little" careful, that it will only happen when someone actually installs snowflake provider. It does not limit "airlfow core" package, so it is highly likely that users who install snowflake provider will not want to run old, unsupported snowflake connector anyway. Also those who want to do it regardless, can still install previous provider. I guess you assesed Airflow as important driver for your adoption - and we absolutely welcome involvement of the stakeholders in our providers in being more active in maintaining them, so I hope this might be a beggining of such cooperation. Happy to review and help to get it merged - will you do it @sfc-gh-rjoshi ? -- 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]
