-
Notifications
You must be signed in to change notification settings - Fork 298
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
[BigQuery, BigQuery Storage]: Add option to use BigQuery Storage API to download results in BigQuery DB-API #16
Comments
The proposal here is to add a Instead of always calling attempt to call the BQ Storage API first. This can be modelled after Just as with Changes from
|
Is your feature request related to a problem? Please describe.
In projects like superset, that use the SQL Alchemy connector, it can be quite slow to download large query results. The BigQuery Storage API speeds this up for
to_dataframe
/ pandas, but not when used via the DB-API / SQL Alchemy. See: googleapis/python-bigquery-sqlalchemy#41Describe the solution you'd like
When creating a DB-API Connection, provide a way to supply a BQ Storage client, in addition to a BQ client. Use this client to download results for the relevant methods in the Cursor object.
Describe alternatives you've considered
Could have a
use_bqstorage_api
option, but this would be inconsistent with the current constructor, which expects a client./cc @yiga2
The text was updated successfully, but these errors were encountered: