[ 
https://issues.apache.org/jira/browse/BEAM-8933?focusedWorklogId=359734&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-359734
 ]

ASF GitHub Bot logged work on BEAM-8933:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 14/Dec/19 01:46
            Start Date: 14/Dec/19 01:46
    Worklog Time Spent: 10m 
      Work Description: TheNeuralBit commented on issue #10369: [BEAM-8933] 
BigQueryIO Arrow for read
URL: https://github.com/apache/beam/pull/10369#issuecomment-565669088
 
 
   Turns out the issue was the incompatible arrow version. The latest Spark 
release, v2.4.4, depends on 0.10. They've upgraded to arrow 0.15.1 for Spark 
v3.0.0.
   
   I force-pushed to my branch, including a downgrade to 0.10.0 which seems to 
fix it. Also put it up as PR #10384 
   There may be some compatibility issues with the BQ Read API though, I'm not 
sure.
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


Issue Time Tracking
-------------------

    Worklog Id:     (was: 359734)
    Time Spent: 2h 50m  (was: 2h 40m)

> BigQuery IO should support read/write in Arrow format
> -----------------------------------------------------
>
>                 Key: BEAM-8933
>                 URL: https://issues.apache.org/jira/browse/BEAM-8933
>             Project: Beam
>          Issue Type: Improvement
>          Components: io-java-gcp
>            Reporter: Kirill Kozlov
>            Assignee: Kirill Kozlov
>            Priority: Major
>          Time Spent: 2h 50m
>  Remaining Estimate: 0h
>
> As of right now BigQuery uses Avro format for reading and writing.
> We should add a config to BigQueryIO to specify which format to use (with 
> Avro as default).



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to