Skip to content

deps: require google-cloud-bigquery-storage to avoid performance warning #414

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

Merged
merged 13 commits into from
Mar 22, 2022
Merged
4 changes: 3 additions & 1 deletion setup.py
Original file line number Diff line number Diff line change
Expand Up @@ -84,7 +84,9 @@ def readme():
# Until this issue is closed
# https://github.com/googleapis/google-cloud-python/issues/10566
"google-auth>=1.25.0,<3.0.0dev", # Work around pip wack.
"google-cloud-bigquery>=2.25.2,<3.0.0dev",
"google-cloud-bigquery>=2.25.2,<4.0.0dev",
"google-cloud-bigquery-storage>=2.0.0,<3.0.0dev",
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Need pyarrow as well. Probably a good thing we're adding this, because I totally missed that.

"pyarrow>=3.0.0,<7.0dev",
# Temporarily set maximimum sqlalchemy to a known-working version while
# we debug failing compliance tests. See:
# https://github.com/googleapis/python-bigquery-sqlalchemy/issues/386
Expand Down
2 changes: 2 additions & 0 deletions testing/constraints-3.6.txt
Original file line number Diff line number Diff line change
Expand Up @@ -7,4 +7,6 @@
sqlalchemy==1.2.0
google-auth==1.25.0
google-cloud-bigquery==2.25.2
google-cloud-bigquery-storage==2.0.0
google-api-core==1.31.5
pyarrow==3.0.0