[
https://issues.apache.org/jira/browse/HADOOP-6323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aaron Kimball updated HADOOP-6323:
----------------------------------
Attachment: HADOOP-6323.5.patch
In the process of writing MAPREDUCE-1126 it has become clear that the
SerializerBase instances themselves are responsible for validating that the
data they are given to serialize matches their metadata, rather than relying on
"client side" checks that they are passing in values of the expected classes.
WritableSerialization now checks that the serialization class matches the
objects it is given. Added a unit test case for this.
This happens implicitly in AvroSerialization based on the schema walking. It
was noted that AvroSerialization reparses the schema for each object it
serializes; this is now memoized in the AvroSerializer instance. One
AvroSerializer should only be used for a single schema.
> Serialization should provide comparators
> ----------------------------------------
>
> Key: HADOOP-6323
> URL: https://issues.apache.org/jira/browse/HADOOP-6323
> Project: Hadoop Common
> Issue Type: New Feature
> Components: io
> Reporter: Doug Cutting
> Assignee: Aaron Kimball
> Attachments: HADOOP-6323.2.patch, HADOOP-6323.3.patch,
> HADOOP-6323.4.patch, HADOOP-6323.5.patch, HADOOP-6323.patch
>
>
> The Serialization interface should permit one to create raw comparators.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
