[ https://issues.apache.org/jira/browse/APEXMALHAR-2034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16129178#comment-16129178 ]
ASF GitHub Bot commented on APEXMALHAR-2034: -------------------------------------------- SaumyaMohan opened a new pull request #666: APEXMALHAR-2034 Adding new Avro Module to encapsulate Container File to Avro GenericRecord to POJO transformations URL: https://github.com/apache/apex-malhar/pull/666 ---------------------------------------------------------------- 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: us...@infra.apache.org > Avro File To POJO Module > ------------------------ > > Key: APEXMALHAR-2034 > URL: https://issues.apache.org/jira/browse/APEXMALHAR-2034 > Project: Apache Apex Malhar > Issue Type: New Feature > Reporter: devendra tagare > Assignee: Saumya Mohan > > Issue: > Avro objects are not serialized by Kryo causing the Avro GenericRecord to not > be available to downstream operators if users don't explicitly mark the > stream locality at container_local or thread_local. > Solution: > This JIRA is used to create a Module on top of AvroFileInputOperator and > AvroToPojo operators such that downstream operators will access POJO instead > of Avro GenericRecord. It, therefore, removes the exposure of GenericRecord > to downstream operators and instead exposes the created POJO to downstream > operators. > In this Module, the stream between the two encapsulated operators > (AvroFileInputOperator and AvroToPojo) is set to CONTAINER_LOCAL. > Along with this new module, existing avro support files are moved from > contrib module to a new 'avro' module. -- This message was sent by Atlassian JIRA (v6.4.14#64029)