Chamikara Jayalath created BEAM-5426:
----------------------------------------
Summary: Use both destination and TableDestination for BQ load job
IDs
Key: BEAM-5426
URL: https://issues.apache.org/jira/browse/BEAM-5426
Project: Beam
Issue Type: Improvement
Components: io-java-gcp
Reporter: Chamikara Jayalath
Assignee: Chamikara Jayalath
Currently we use TableDestination when creating a unique load job ID for a
destination:
[https://github.com/apache/beam/blob/master/sdks/java/io/google-cloud-platform/src/main/java/org/apache/beam/sdk/io/gcp/bigquery/BigQueryHelpers.java#L359]
This can result in a data loss issue if a user returns the same
TableDestination for different destination IDs. I think we can prevent this if
we include both IDs in the BQ load job ID.
CC: [~reuvenlax]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
