Repository navigation
#26789 Fix auto schema update when schema order has changed. - #26794
Conversation
|
Assigning reviewers. If you would like to opt out of this review, comment R: @Abacn for label java. Available commands:
The PR bot will only process comments in the main thread (not review comments). |
There was a problem hiding this comment.
done in other unit test
There was a problem hiding this comment.
is this return too aggresive?
There was a problem hiding this comment.
I don't think so - it means that the nested row was incompatible (essentially a field was deleted). In theory we should never hit this of course, since BigQuery should never allow the table to be updated to an incompatible schema.
480306b to
e8b593a
Compare
|
Run Spotless PreCommit |
|
Run Java_GCP_IO_Direct PreCommit |
|
run java precommit |
| .addFields( | ||
| TableFieldSchema.newBuilder().setName("c").setType(TableFieldSchema.Type.STRING)) | ||
| .addFields( | ||
| TableFieldSchema.newBuilder() |
There was a problem hiding this comment.
more than one layer nested?
There was a problem hiding this comment.
added another layer.
|
run java precommit |
1 similar comment
|
run java precommit |
…when schema order has changed.
…order has changed. (#26810) Co-authored-by: reuvenlax <relax@google.com>
…when schema order has changed.
R: @yirutang