[
https://issues.apache.org/jira/browse/BEAM-7570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aaron Liblong updated BEAM-7570:
--------------------------------
Description:
A function in BigQueryIO.Write called withCustomGcsTempLocation allows
specification at template execution time of a GCS location used by BigQuery to
write temp files. BigQuery also needs to write temp files for _read_
operations, and therefore this function should be available in BigQueryIO.Read.
This issue blocks the ability to deploy a template with BigQuery read ops to an
environment where users (who will execute the template) have only read access.
was:A function in BigQueryIO.Write called withCustomGcsTempLocation allows
specification at template execution time of a GCS location used by BigQuery to
write temp files. BigQuery also needs to write temp files for _read_
operations, and therefore this function should be available in BigQueryIO.Read.
> withCustomGcsTempLocation should also be implemented for BigQueryIO.Read
> ------------------------------------------------------------------------
>
> Key: BEAM-7570
> URL: https://issues.apache.org/jira/browse/BEAM-7570
> Project: Beam
> Issue Type: Improvement
> Components: io-java-gcp
> Reporter: Aaron Liblong
> Priority: Major
>
> A function in BigQueryIO.Write called withCustomGcsTempLocation allows
> specification at template execution time of a GCS location used by BigQuery
> to write temp files. BigQuery also needs to write temp files for _read_
> operations, and therefore this function should be available in
> BigQueryIO.Read.
> This issue blocks the ability to deploy a template with BigQuery read ops to
> an environment where users (who will execute the template) have only read
> access.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
