Skip to content
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

Map BigQuery DB-API onto a SQLAlchemy dialect #3603

Closed
tswast opened this issue Jul 12, 2017 · 1 comment
Closed

Map BigQuery DB-API onto a SQLAlchemy dialect #3603

tswast opened this issue Jul 12, 2017 · 1 comment
Assignees
Labels
api: bigquery Issues related to the BigQuery API. type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.

Comments

@tswast
Copy link
Contributor

tswast commented Jul 12, 2017

This would allow BigQuery to be used from the BI tool, Superset, among other places.

Relevant SQLAlchemy docs:

@tswast tswast added api: bigquery Issues related to the BigQuery API. priority: p2 Moderately-important priority. Fix may not be included in next release. type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design. labels Jul 12, 2017
@lukesneeringer lukesneeringer removed the priority: p2 Moderately-important priority. Fix may not be included in next release. label Aug 9, 2017
@lukesneeringer
Copy link
Contributor

In an effort to get my project management to be a bit more sane, I am going to try something else in lieu of single issues that represent large projects.

I have referenced this on a wiki page devoted to our significant feature backlog. Discussion of this particular feature is still welcome here, although I am going to close this issue until such time as this is something we take on.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api: bigquery Issues related to the BigQuery API. type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.
Projects
No open projects
Development

No branches or pull requests

2 participants