[
https://issues.apache.org/jira/browse/GOBBLIN-238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhixiong Chen updated GOBBLIN-238:
----------------------------------
Description:
The current implementation of EnvelopeSchemaConverter has several flaws:
- Assumes top level payload schema field
- Output record is the schema'ed payload but output schema is a String
The task implements two types of EnvelopeSchemaConverter:
EnvelopePayloadConverter and
{code:java}
converter.envelopeSchemaConverter.schemaIdField="metadata.payloadSchemaId"
{code}
was:
The current implementation of EnvelopeSchemaConverter only recognizes top level
payload schema and bytes fields. This task is to support nested payload schema
and bytes fields. For example, the converter will extract the payload with the
following configurations:
{code:java}
EnvelopeSchemaConverter.schemaIdField="metadata.payloadSchemaId"
EnvelopeSchemaConverter.payloadField="nestedRecord.payload"
{code}
> Implement EnvelopePayloadConverter and EnvelopeSchemaDecorator
> --------------------------------------------------------------
>
> Key: GOBBLIN-238
> URL: https://issues.apache.org/jira/browse/GOBBLIN-238
> Project: Apache Gobblin
> Issue Type: Task
> Reporter: Zhixiong Chen
> Assignee: Zhixiong Chen
> Labels: Core:Converter
>
> The current implementation of EnvelopeSchemaConverter has several flaws:
> - Assumes top level payload schema field
> - Output record is the schema'ed payload but output schema is a String
> The task implements two types of EnvelopeSchemaConverter:
> EnvelopePayloadConverter and
> {code:java}
> converter.envelopeSchemaConverter.schemaIdField="metadata.payloadSchemaId"
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
