Skip to content

The java bigquery library expects more values to be returned from an update table call than currently returned #363

@KasperJanssens

Description

@KasperJanssens

What happened?

When performing an update call, e.g. adding a column,for instance with this payload to an existing table called campaigns here
{ "schema" : { "fields" : [ { "name" : "bleuh", "type" : "STRING" } ] }, "tableReference" : { "datasetId" : "service", "projectId" : "test-project", "tableId" : "campaigns" } }
The json being returned is exactly the json that has been sent. The java library expects at least the table type to be present as well (will throw an exception)

What did you expect to happen?

I expect the table update call to function when adding a column, likely by returning an instance of 'table'. At the least the table type ("TABLE, VIEW, EXTERNAL, SNAPSHOT, ...) seems to be expected and needed by the library.

How can we reproduce it (as minimally and precisely as possible)?

any java update table call will have this issue. When performing an update through curl, you can also see that the table key is not returned, it reflects the input json it seems

Anything else we need to know?

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions