You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@crunch.apache.org by "Josh Wills (JIRA)" <ji...@apache.org> on 2013/12/19 21:07:07 UTC
[jira] [Updated] (CRUNCH-312) Correctly determine the right
DatumReader/Writer to use for Avro derived types
[ https://issues.apache.org/jira/browse/CRUNCH-312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Josh Wills updated CRUNCH-312:
------------------------------
Attachment: CRUNCH-312.patch
Patch for this, along with an integration test that demonstrates the issue w/the StringWrapper reflection type.
> Correctly determine the right DatumReader/Writer to use for Avro derived types
> ------------------------------------------------------------------------------
>
> Key: CRUNCH-312
> URL: https://issues.apache.org/jira/browse/CRUNCH-312
> Project: Crunch
> Issue Type: Bug
> Components: Core
> Affects Versions: 0.9.0
> Reporter: Josh Wills
> Assignee: Josh Wills
> Attachments: CRUNCH-312.patch
>
>
> Derived AvroTypes are only linked to their base AvroTypes by their schema, and so any information about how the base type needs to be read (e.g., using reflect/specific/generic datumreader/writer) is lost when the derived type is created. We need to provide a link between the record type of the base AvroType and its derived type so that derived types can be read properly.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)