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

BigQuery: support Tables: patch #1564

Closed
juhoautio opened this issue Jan 25, 2017 · 5 comments
Closed

BigQuery: support Tables: patch #1564

juhoautio opened this issue Jan 25, 2017 · 5 comments
Assignees
Labels
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.

Comments

@juhoautio
Copy link

Add support for this:
https://cloud.google.com/bigquery/docs/reference/rest/v2/tables/patch

..unless it's already somehow possible to add or modify a field without specifying all the existing fields?

Internally BigQueryImpl.update seems to call bigQueryRpc.patch, but when I tried to call BigQuery.update with only one field (the field to be added), I got an error that the schema doesn't match with the existing one.

@garrettjonesgoogle garrettjonesgoogle added api: bigquery Issues related to the BigQuery API. type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design. labels Jan 26, 2017
@tcoffee-google tcoffee-google added the priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. label Jun 12, 2017
@juhoautio
Copy link
Author

I'm not actively working on this any more, so from my perspective this issue could be closed any way.

But is that a recently added method or was it there already on January 25th? The javadoc on BigQueryRpc#patch seems to match with https://cloud.google.com/bigquery/docs/reference/rest/v2/tables/patch, so it seems to be what I was looking for back in the day.

@tcoffee-google
Copy link
Contributor

Internally BigQueryImpl.update seems to call bigQueryRpc.patch, but when I tried to call BigQuery.update with only one field (the field to be added), I got an error that the schema doesn't match with the existing one.

After looking closely, this still seems odd to me. @garrettjonesgoogle before I try to reproduce it, any idea why this would be the case?

@garrettjonesgoogle
Copy link
Member

@tcoffee-google No, I haven't worked with this functionality yet.

@tcoffee-google tcoffee-google self-assigned this Jun 14, 2017
@garrettjonesgoogle garrettjonesgoogle added priority: p2 Moderately-important priority. Fix may not be included in next release. and removed priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. triaged for GA labels Aug 8, 2017
@garrettjonesgoogle
Copy link
Member

I'm going to close this since the requester has stated they don't need it.

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. 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.
Projects
None yet
Development

No branches or pull requests

4 participants