[
https://issues.apache.org/jira/browse/BEAM-13140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17438998#comment-17438998
]
In-Ho Yi commented on BEAM-13140:
---------------------------------
I'm bumping into this issue in production in one of our long-running bigquery
writes. Is there a workaround while we wait for the patch to land?
> WriteRename not using loadJobProjectId configuration from BigQueryIO
> --------------------------------------------------------------------
>
> Key: BEAM-13140
> URL: https://issues.apache.org/jira/browse/BEAM-13140
> Project: Beam
> Issue Type: Bug
> Components: io-java-gcp
> Reporter: Hector Lagos
> Priority: P2
> Time Spent: 6h 10m
> Remaining Estimate: 0h
>
> [WriteRename|https://github.com/apache/beam/blob/v2.31.0/sdks/java/io/google-cloud-platform/src/main/java/org/apache/beam/sdk/io/gcp/bigquery/WriteRename.java#L221]
> is not using `BigQueryIO.withLoadJobProjectId` like
> [WriteTables|https://github.com/apache/beam/blob/v2.31.0/sdks/java/io/google-cloud-platform/src/main/java/org/apache/beam/sdk/io/gcp/bigquery/WriteTables.java]
> at the JobReference instantiation. The above makes the job fails if the
> service account only has permissions on the `LoadJobProjectId` for bq job
> creation.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
