[
https://issues.apache.org/jira/browse/HADOOP-6120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733194#action_12733194
]
Sharad Agarwal commented on HADOOP-6120:
----------------------------------------
bq. JavaSerialization was written more to demonstrate the generality of the
abstraction
I am fine removing JavaSerialization from the defaults, if folks think it will
discourage people to use java serialization.
bq. folks can configure a given class to be serialized in different ways.
Do you mean that accept(Class<?> c) should select serialization not only based
on class but also based on the meta data passed ? We need to change accept as
well, no ?
bq. Perhaps this belongs in another Jira, but without it we're missing out on a
lot of Avro's functionality.
I think this can be discussed in another Jira, as the current implementation
should be fine in case reader and writer are for same schema. We can start
using this in mapreduce jobs.
> 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.
