[
https://issues.apache.org/jira/browse/BEAM-3433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Peterson updated BEAM-3433:
---------------------------------
Fix Version/s: 2.5.0
> Allow BigQueryIO to use a different project for the load job in batch mode.
> ---------------------------------------------------------------------------
>
> Key: BEAM-3433
> URL: https://issues.apache.org/jira/browse/BEAM-3433
> Project: Beam
> Issue Type: Bug
> Components: io-java-gcp
> Reporter: Kevin Peterson
> Assignee: Chamikara Jayalath
> Priority: Minor
> Fix For: 2.5.0
>
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> BigQueryIO is currently configured to always run a batch load job using the
> same projects as the destination table:
> https://github.com/apache/beam/blob/192b4c70927901860312f8c8acd27bd47e4a4259/sdks/java/io/google-cloud-platform/src/main/java/org/apache/beam/sdk/io/gcp/bigquery/WriteTables.java#L256
> This may not always be desirable, since a pipeline may have write access to a
> dataset in a different project, but not jobs.create access in that project.
> This parameter should be settable in the interface.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
