-
Notifications
You must be signed in to change notification settings - Fork 14.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update google-cloud deps to v2 #12116
Comments
Thanks @mik-laj . You are a gem! |
I am working on Dataproc package. |
If we want users to be able to install backport packages, we should also remember about the limitations that exist in Airflow 1.10 We don't support them anymore, but users can still use them and it would be great if they could use new and old operators at the same time.
We can only update these operators when we stop releasing backport packages.
CC: @rafalbiegacz @potiuk |
@michalslowikowski00 @turbaszek Fortunately, Dataproc does not conflict, but other libraries will cause problems. |
I added a new column "To update?", which specifies whether we can update this library or rather we should wait until we drop Airflow 1.10 support. |
Part of: #12120 |
Hello,
Google Cloud API Libraries introduced breaking changes in 2.0.0 (https://github.com/googleapis/python-container/blob/master/UPGRADING.md) and they already caused a number of changes. For this reason, we limit all our google-cloud deps to <2.0.0. This limit means our updates will not receive updates, but everything will still work.
We should try to update all operators to use newer versions so that our users can use the newest API features.
You can track progress using this notebook:
https://colab.research.google.com/drive/1F5Lw8qNcxCvWaYUrGZ1x3W3v3080Dq0U#scrollTo=2IjL5GZH4PY_
Related issue: #10316
The text was updated successfully, but these errors were encountered: