-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
API not respecting destination table #1786
Comments
You never called |
Table creation shouldn't be an issue according this: https://cloud.google.com/bigquery/docs/reference/v2/jobs configuration.copy.createDisposition Default is: "CREATE_IF_NEEDED: If the table does not exist, BigQuery creates the table." |
D'oh! My bad. |
@ToddMorrill I cannot reproduce here: your example triggers an attribute error for When I correct it to |
Much appreciated, looks like it's just a matter of documentation. See here, where it is still being called "job.destination_table" https://googlecloudplatform.github.io/gcloud-python/stable/bigquery-usage.html |
Following the example at https://googlecloudplatform.github.io/gcloud-python/stable/bigquery-usage.html#querying-data-asynchronous the destination table does not appear to be respected
Reproduction steps and observed behavior:
Job has
write_disposition
:WRITE_TRUNCATE
anddestination table_id
:"anon6f3505ba6efbcaaa685e4812bf5e132db2bb343a"
Expected behavior: Job should have created a new table called beth_only and set write disposition to
WRITE_EMPTY
The text was updated successfully, but these errors were encountered: