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

Posted to commits@beam.apache.org by "Daniel (JIRA)" <ji...@apache.org> on 2018/05/21 14:36:00 UTC

[jira] [Commented] (BEAM-1909) BigQuery read transform fails for DirectRunner when querying non-US regions

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

Daniel commented on BEAM-1909:
------------------------------

Using this pattern, would you people be happy with code that extracts the dataset from the query and determines its location.

Something like 
```
SELECT field FROM dataset.table 
```
Would return dataset.table.
In the case that there are joins or views, it won't matter as they all need to be in the same region so I'll take the first one.

Let me know I'll start working on it.

> BigQuery read transform fails for DirectRunner when querying non-US regions
> ---------------------------------------------------------------------------
>
>                 Key: BEAM-1909
>                 URL: https://issues.apache.org/jira/browse/BEAM-1909
>             Project: Beam
>          Issue Type: Bug
>          Components: sdk-py-core
>            Reporter: Chamikara Jayalath
>            Priority: Major
>
> See: http://stackoverflow.com/questions/42135002/google-dataflow-cannot-read-and-write-in-different-locations-python-sdk-v0-5-5/42144748?noredirect=1#comment73621983_42144748
> This should be fixed by creating the temp dataset and table in the correct region.
> cc: [~sb2nov]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)