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

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

                Author: ASF GitHub Bot
            Created on: 18/Dec/19 02:06
            Start Date: 18/Dec/19 02:06
    Worklog Time Spent: 10m 
      Work Description: TheNeuralBit commented on issue #10384: [WIP] 
[BEAM-8933] Utilities for converting Arrow schemas and reading Arrow batches as 
Rows
URL: https://github.com/apache/beam/pull/10384#issuecomment-566833607
 
 
   Pushed a commit that moved the arrow code into `:sdks:java:extension:arrow`, 
thanks for the suggestion @iemejia. I want to do a little more clean up 
tomorrow before sending this out for review but it should be enough for 
@11moon11 to work from for the gcp io changes.
 
----------------------------------------------------------------
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: 361264)
    Time Spent: 3h 40m  (was: 3.5h)

> 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: 3h 40m
>  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: Arrow or 
> Avro (with Avro as default).



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

Reply via email to