Skip to content

Conversation

@pongad
Copy link
Contributor

@pongad pongad commented Dec 11, 2017

Fixes #2678.

If the param is an empty array, the server sends us
a null value, not a value with empty array.
This commit makes us detect nulls properly.

Also move to AutoValue. This fixes a latent bug where the array value
might be mutable.

Fixes #2678.

If the param is an empty array, the server sends us
a null value, not a value with empty array.
This commit makes us detect nulls properly.

Also move to AutoValue. This fixes a latent bug where the array value
might be mutable.
@googlebot googlebot added the cla: yes This human has signed the Contributor License Agreement. label Dec 11, 2017
Copy link
Contributor

@tswast tswast left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Regarding AutoValue, I assume that in the actual released package users will not need any compiler plugins, right? We've encountered a lot of trouble when people use samples with AutoValue (mostly with people using the built-in Eclipse compiler and not Maven directly), but I think in the case of samples the compiler plugin is unavoidable.

@pongad
Copy link
Contributor Author

pongad commented Dec 11, 2017

Yup! Our tools should auto-generate the AutoValue classes and package them along with other things sent to Maven. The users shouldn't know we're using AutoValue aside from the fact that docs will have abstract declaration.

Will hold off until GCJ releases.

@pongad pongad merged commit 973ffc1 into googleapis:master Dec 12, 2017
@pongad pongad deleted the bq-zero-arr branch December 12, 2017 23:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cla: yes This human has signed the Contributor License Agreement.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bigquery] Empty arrays are not supported as query parameter values

3 participants