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

ASF GitHub Bot commented on BEAM-1909:
--------------------------------------

GitHub user ubunatic opened a pull request:

    https://github.com/apache/beam/pull/2582

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

    **Note**: This is an updated and condensed PR for the original PR: 
https://github.com/apache/beam/pull/2509
    
    **Description**:
    I partially (!) fixed the issue by getting the location of the source 
table. Then I use this location as location of the created temp dataset. The 
added parameters are optional and should not break anything.
    
    **Tests**: I tested with an US and EU dataset as source in a 
`DirectRunner`, i.e., using a `BigQuerySource` with `table=<some-table>`.
    
    **What's missing**: It does not work for a `BigQuerySource` with 
`query=<some-query>`.
    
    The corresponding Jira issue should not yet be closed.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/ubunatic/beam 
set-temp-table-region-for-table-source

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/beam/pull/2582.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #2582
    
----
commit 615f6fad7930819748c5fec3a2b313f137ef8c6f
Author: Uwe Jugel <[email protected]>
Date:   2017-04-12T12:56:50Z

    add temp dataset location for non-query BigQuerySource

----


> 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
>            Reporter: Chamikara Jayalath
>
> 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
(v6.3.15#6346)

Reply via email to