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

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

                Author: ASF GitHub Bot
            Created on: 16/Dec/20 18:07
            Start Date: 16/Dec/20 18:07
    Worklog Time Spent: 10m 
      Work Description: TheNeuralBit commented on pull request #13428:
URL: https://github.com/apache/beam/pull/13428#issuecomment-746747754


   @ccciudatu Yeah I don't think we have existing interfaces that could support 
this, we'd need to design something. I haven't thought too much about this 
aside from recognizing "this is something we keep duplicating, there should 
probably be a pluggable interface to abstract it". Sorry to distract the 
conversation - I'd be +1 for just adding thrift support to KafkaTableProvider 
for now. There's no reason we couldn't generalize it later


----------------------------------------------------------------
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: 525177)
    Time Spent: 6h 40m  (was: 6.5h)

> Beam schema for thrift data
> ---------------------------
>
>                 Key: BEAM-11338
>                 URL: https://issues.apache.org/jira/browse/BEAM-11338
>             Project: Beam
>          Issue Type: New Feature
>          Components: io-java-utilities
>            Reporter: Costi Ciudatu
>            Assignee: Costi Ciudatu
>            Priority: P2
>              Labels: thrift
>             Fix For: 2.27.0
>
>          Time Spent: 6h 40m
>  Remaining Estimate: 0h
>
> Define a SchemaProvider that can handle thrift objects, the same way as 
> ProtoMessageSchema handles protobuf.



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

Reply via email to