[
https://issues.apache.org/jira/browse/BEAM-10182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17548569#comment-17548569
]
Danny McCormick commented on BEAM-10182:
----------------------------------------
This issue has been migrated to https://github.com/apache/beam/issues/20200
> Support custom gcs location for bigquery read
> ---------------------------------------------
>
> Key: BEAM-10182
> URL: https://issues.apache.org/jira/browse/BEAM-10182
> Project: Beam
> Issue Type: Improvement
> Components: sdk-java-core
> Reporter: Ning
> Priority: P3
> Labels: Clarified
>
> Java and Python handles the usage of temp location for bigquery io
> differently.
> Java's Read only uses and validates tempLocation but Write takes
> customGcsLocation and falls back to tempLocation.
> Python's Read takes gcs_location and falls back to temp_location while Write
> takes custom_gcs_temp_location and falls back to temp_location.
> We need an equivalence of
> https://github.com/apache/beam/blob/0a0399f71cf14ecabe7e73b6cd596325bb7ff2ea/sdks/java/io/google-cloud-platform/src/main/java/org/apache/beam/sdk/io/gcp/bigquery/BigQueryIO.java#L2314
> for the Read class.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
