[
https://issues.apache.org/jira/browse/BEAM-8933?focusedWorklogId=575621&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-575621
]
ASF GitHub Bot logged work on BEAM-8933:
----------------------------------------
Author: ASF GitHub Bot
Created on: 01/Apr/21 17:21
Start Date: 01/Apr/21 17:21
Worklog Time Spent: 10m
Work Description: emkornfield commented on pull request #10384:
URL: https://github.com/apache/beam/pull/10384#issuecomment-812054496
> I am a bit worried of adding arrow to core, I know Arrow is fantastic but
can we envision to package this as an extension? My point is the extra
dependencies, in particular netty that has proved to be a total PITA in the
past with runners like Spark.
As an update Arrow has now decoupled from the need to netty as a compile
time dependency (memory allocation implementations have been separated into
separate modules). I think the two potentially remaining problematic
dependencies might be jackson and SLF4j
--
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:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 575621)
Time Spent: 13h 20m (was: 13h 10m)
> BigQuery IO should support reading Arrow format over Storage API
> ----------------------------------------------------------------
>
> 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: Isidro Martinez
> Priority: P3
> Time Spent: 13h 20m
> 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)
