[
https://issues.apache.org/jira/browse/HADOOP-6120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12732716#action_12732716
]
Doug Cutting commented on HADOOP-6120:
--------------------------------------
Sigh. I just reallized this is really fragile, since we don't permit one to
specify a different schema to read things.
We need to get metadata from the serializer used to write data to the
deserializer used to deserialize it. For even Writable, we should check that
the data was indeed written with WritableSerializer, since folks can configure
a given class to be serialized in different ways.
So we might add methods like:
- Deserializer Serialization#getDeserializer(Map<String,String> meta);
- Serializer Serialization#getSerializer(Map<String,String> meta);
- Map<String,String> Serializer#getMeta();
And alter, e.g. SequenceFile and other containers to use these.
Perhaps this belongs in another Jira, but without it we're missing out on a lot
of Avro's functionality.
> Add support for Avro types in hadoop
> ------------------------------------
>
> Key: HADOOP-6120
> URL: https://issues.apache.org/jira/browse/HADOOP-6120
> Project: Hadoop Common
> Issue Type: New Feature
> Reporter: Sharad Agarwal
> Assignee: Sharad Agarwal
> Attachments: 6120_v1.patch, 6120_v2.patch, 6120_v3.patch,
> 6120_v4.patch, 6120_v5.patch, HADOOP-6120.patch
>
>
> Support to serialize and deserialize Avro types in Hadoop.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
