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

Implement a BigQuery runner for the query library #180

Closed
bashir2 opened this issue Jun 25, 2021 · 1 comment
Closed

Implement a BigQuery runner for the query library #180

bashir2 opened this issue Jun 25, 2021 · 1 comment
Assignees
Labels
enhancement New feature or request P2:should An issue to be addressed in a quarter or so.

Comments

@bashir2
Copy link
Collaborator

bashir2 commented Jun 25, 2021

With the new approach to our query library API, the underlying runner for distributed data processing is completely separated from how the end user of the library, uses the generated Pandas DataFrames. Our current focus is the Spark runner but we will need a BigQuery based implementation too, i.e., implementing this class.

The new query API is a work in progress and we should focus on BigQuery runner only after we are fairly confident the query API is good enough for the immediate use-cases we have.

@bashir2 bashir2 added enhancement New feature or request P2:should An issue to be addressed in a quarter or so. labels Jun 25, 2021
@omarismail94 omarismail94 self-assigned this Jun 26, 2021
@gdevanla gdevanla linked a pull request Apr 3, 2022 that will close this issue
6 tasks
@bashir2 bashir2 assigned gdevanla and unassigned omarismail94 May 9, 2022
bashir2 pushed a commit that referenced this issue Jun 28, 2022
@bashir2
Copy link
Collaborator Author

bashir2 commented Jul 5, 2022

This is implemented in PR #269.

@bashir2 bashir2 closed this as completed Jul 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request P2:should An issue to be addressed in a quarter or so.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants