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

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

                Author: ASF GitHub Bot
            Created on: 23/Oct/18 23:38
            Start Date: 23/Oct/18 23:38
    Worklog Time Spent: 10m 
      Work Description: akedin commented on issue #6777: [BEAM-5807] Conversion 
from AVRO records to rows
URL: https://github.com/apache/beam/pull/6777#issuecomment-432459588
 
 
   Looks like our build is especially broken in the last few days :( Next 
problem problem: https://github.com/apache/beam/pull/6807

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on 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: 157892)
    Time Spent: 5h  (was: 4h 50m)

> Add AvroIO.readRows
> -------------------
>
>                 Key: BEAM-5807
>                 URL: https://issues.apache.org/jira/browse/BEAM-5807
>             Project: Beam
>          Issue Type: Improvement
>          Components: dsl-sql
>            Reporter: Gleb Kanterov
>            Assignee: Gleb Kanterov
>            Priority: Major
>          Time Spent: 5h
>  Remaining Estimate: 0h
>
> # Motivation
> At the moment the only way to read AVRO is through code generation with 
> avro-compiler and JavaBeanSchema. It makes it not possible to write 
> transforms that can work with dynamic schemas. AVRO has generic data type 
> called GenericRecord, reading is implemented in AvroIO.
> readGenericRecords. There is a code to convert GenericRecord to Row shipped 
> as a part of BigQueryIO. However, it doesn't support all types and nested 
> records.



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

Reply via email to