8000 API not respecting destination table · Issue #1786 · googleapis/google-cloud-python · GitHub
[go: up one dir, main page]

Skip to content

API not respecting destination table #1786

@mattjo

Description

@mattjo

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:

QUERY = 'SELECT * FROM [dataset.babynames] where name = "Beth"'
dataset = client.dataset('dataset')
table = dataset.table(name='only_beth')
job = client.run_async_query('only_beth', QUERY)
job.destination_table = table
job.write_disposition = 'WRITE_EMPTY'
job.begin()
job.reload()
job.state
'DONE'

Job has write_disposition: WRITE_TRUNCATE and destination table_id: "anon6f3505ba6efbcaaa685e4812bf5e132db2bb343a"

Expected behavior: Job should have created a new table called beth_only and set write disposition to WRITE_EMPTY

Metadata

Metadata

Assignees

Labels

api: bigqueryIssues related to the BigQuery API.type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions

    0