[jira] [Commented] (BEAM-10182) Support custom gcs location for bigquery read

["Beam JIRA Bot (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/BEAM-10182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17192329#comment-17192329 ] 

Beam JIRA Bot commented on BEAM-10182:
--------------------------------------

This issue is P2 but has been unassigned without any comment for 60 days so it has been labeled "stale-P2". If this issue is still affecting you, we care! Please comment and remove the label. Otherwise, in 14 days the issue will be moved to P3.

Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed explanation of what these priorities mean.


> 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 Kang
>            Priority: P2
>              Labels: stale-P2
>
> 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.3.4#803005)