You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@beam.apache.org by "Kevin Peterson (JIRA)" <ji...@apache.org> on 2018/01/08 21:23:00 UTC

[jira] [Created] (BEAM-3433) Allow BigQueryIO to use a different project for the load job in batch mode.

Kevin Peterson created BEAM-3433:
------------------------------------

             Summary: 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: sdk-java-gcp
            Reporter: Kevin Peterson
            Assignee: Chamikara Jayalath
            Priority: Minor


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
(v6.4.14#64029)