You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by "Matti Remes (JIRA)" <ji...@apache.org> on 2017/08/15 14:25:00 UTC
[jira] [Created] (BEAM-2768) Fix bigquery.WriteTables generating
non-unique job identifiers
Matti Remes created BEAM-2768:
---------------------------------
Summary: Fix bigquery.WriteTables generating non-unique job identifiers
Key: BEAM-2768
URL: https://issues.apache.org/jira/browse/BEAM-2768
Project: Beam
Issue Type: Bug
Components: beam-model
Affects Versions: 2.0.0
Reporter: Matti Remes
Assignee: Kenneth Knowles
This is a result of BigQueryIO not creating unique job ids for batch inserts, thus BigQuery API responding with a 409 conflict error:
{code:java}
Request failed with code 409, will NOT retry: https://www.googleapis.com/bigquery/v2/projects/<project_id>/jobs
{code}
The jobs are initiated in a step BatchLoads/SinglePartitionWriteTables, called by step's WriteTables ParDo:
https://github.com/apache/beam/blob/master/sdks/java/io/google-cloud-platform/src/main/java/org/apache/beam/sdk/io/gcp/bigquery/BatchLoads.java#L511-L521
https://github.com/apache/beam/blob/master/sdks/java/io/google-cloud-platform/src/main/java/org/apache/beam/sdk/io/gcp/bigquery/WriteTables.java#L148
It would probably be a good idea to append a UUIDs as part of the job id.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)