-
Notifications
You must be signed in to change notification settings - Fork 139
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
Conversation
The wrapped DB-API uses google-cloud-bigquery-storage to download query results by default. It raises a warning and falls back to the REST API if google-cloud-bigquery-storage is not installed. deps: allow google-cloud-bigquery version 3.x
@@ -84,7 +84,8 @@ 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", |
There was a problem hiding this comment.
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.
Sorry, something went wrong.
All reactions
parthea
stephaniewang526
Successfully merging this pull request may close these issues.
None yet
The wrapped DB-API uses google-cloud-bigquery-storage to download query
results by default. It raises a warning and falls back to the REST API
if google-cloud-bigquery-storage is not installed.
The google-cloud-bigquery version 3.x library is tested in #401 and it does not include any breaking changes that should affect the SQLAlchemy connector.
deps: allow google-cloud-bigquery version 3.x
Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly:
Fixes #<issue_number_goes_here> 🦕