- Notifications
You must be signed in to change notification settings - Fork1.6k
BigQuery: add destination table properties to 'LoadJobConfig'.#6202
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
tswast left a comment
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!
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
tseaver commentedOct 17, 2018
Merge blocked pending resolution of#6231, and a re-run of the |
tseaver commentedOct 17, 2018
None are relevant to this PR, which is purely BigQuery. @theacodes looks like Kokoro has gone from skipping everything (#6231) to running all tests regardless? |
Note question posted to issue#5093: should 'max_bad_rows' and'skip_leading_rows' match in how the mangle / parse the value in theresource? Docs say it is an integer.
…ryption_configuration'.
It should remove the 'timePartitioning' sub-key altogether.
… LJC tests.Fix bug revealed thereby in 'LJC.destination_encryption_configuration' setter.
554b323 to2a920d1Compare
Closes#5093.
This PR includes a bunch of new explicit unit test cases / assertions for
LoadJobConfig, and reorders the properties alphabetically, to make it easier to match up with the docs./cc@yiga2.