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
google bigquery implementation complete #123
google bigquery implementation complete #123
Conversation
@poundifdef this is ready for review |
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.
Thanks for the quick work here. I've left some comments and questions.
[MOD] fixed download to io.Copy [MOD] removed redudant fields [MOD] no need for ordering columns in CSV
@poundifdef this is ready for review |
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.
Thank you - I've tested this and it is almost ready to go. Just a few small changes.
…stream to raw sql, [MOD] file deelte support.
@poundifdef added changes |
This branch does not work any longer.
Gives this error:
You probably want to use this api, right? https://cloud.google.com/bigquery/docs/datasets#go |
…stream to raw sql, [MOD] file deelte support.
So split and create the dataset first? |
Yes. The goal is for the user to do as little configuration as possible, so if we can automate creating a dataset then that is what I'd like to do. |
I will need location parameter, take it from user in config? |
Yes |
How about get query here? What if dataset and table not there? Create and return empty? |
If a user tries to query and the dataset or table does not exist, then we should just return the error that BigQuery throws. We only automatically create tables when the user inserts data. |
That is exactly for current case, pushing. |
4000868
to
b410134
Compare
@poundifdef pushed the changes |
Thank you for your persistence. I still get an error when running the same test as above:
Here is the error:
I believe this is because BigQuery's |
You are right @poundifdef, that's the case of |
@poundifdef got chance to test this? |
/claim #115
/closes #115
@poundifdef Some thigs to take care:
dataset.table
, may be need to somewhere in docsScreenshots: