[
https://issues.apache.org/jira/browse/BEAM-3433?focusedWorklogId=96186&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-96186
]
ASF GitHub Bot logged work on BEAM-3433:
----------------------------------------
Author: ASF GitHub Bot
Created on: 27/Apr/18 18:49
Start Date: 27/Apr/18 18:49
Worklog Time Spent: 10m
Work Description: jkff commented on a change in pull request #5178:
[BEAM-3433] Allow a GCP project to be explicitly set for a load job
URL: https://github.com/apache/beam/pull/5178#discussion_r184776409
##########
File path:
sdks/java/io/google-cloud-platform/src/main/java/org/apache/beam/sdk/io/gcp/bigquery/BigQueryIO.java
##########
@@ -1391,6 +1394,16 @@ static String getExtractDestinationUri(String
extractDestinationDir) {
return toBuilder().setMethod(method).build();
}
+ /**
+ * Set the project the BigQuery load job will be initiated from. This is
only applicable when
+ * the write method is set to {@link Method#FILE_LOADS}. If omitted, the
project of the
+ * destination table is used.
+ */
+ public Write<T> withLoadJobProjectId(String loadJobProjectId) {
Review comment:
Could you add a ValueProvider version too?
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 96186)
Time Spent: 40m (was: 0.5h)
> 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
> Time Spent: 40m
> 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)
