[
https://issues.apache.org/jira/browse/BEAM-881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismaël Mejía resolved BEAM-881.
-------------------------------
Fix Version/s: Not applicable
Assignee: (was: Jean-Baptiste Onofré)
Resolution: Won't Fix
As pointed by [~rskraba] the canonical approach now on Beam is to do Beam Row
for this, so not worth to do this.
> 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: io-ideas
> Reporter: Jean-Baptiste Onofré
> Priority: Major
> Fix For: Not applicable
>
>
> 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
(v8.3.4#803005)
