You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org> on 2017/01/17 23:21:26 UTC

[jira] [Commented] (BEAM-881) Provide a PTransform in IOs providing a "standard" Avro IndexedRecord

    [ https://issues.apache.org/jira/browse/BEAM-881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15827026#comment-15827026 ] 

Jean-Baptiste Onofré commented on BEAM-881:
-------------------------------------------

[~davor] [~kenn] [~bchambers] as discussed together, here's the Jira about providing {{PTransform}} in each IO to deal with type conversion.

> Provide a PTransform in IOs providing a "standard" Avro IndexedRecord
> ---------------------------------------------------------------------
>
>                 Key: BEAM-881
>                 URL: https://issues.apache.org/jira/browse/BEAM-881
>             Project: Beam
>          Issue Type: New Feature
>          Components: sdk-java-extensions
>            Reporter: Jean-Baptiste Onofré
>            Assignee: Jean-Baptiste Onofré
>
> Now, each IO is using a different data format. For instance, the {{JmsIO.Read}} provides a {{PCollection}} of {{JmsRecord}} (and {{JmsIO.Write}} expects also a {{JmsRecord}}), {{KafkaIO.Read}} provides a {{PCollection}} of {{KafkaRecord}}.
> It could appear a bit "complex" for users to manipulate such kind of data format: some users may expect kind of standard format.
> Without modifying the existing IO, we could add a {{PTransform}} (as part of the IO) that an user can optionally use. This transform will convert the IO data format (let say {{JmsRecord}} for instance) to a standard Avro {{IndexedRecord}}.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)