[
https://issues.apache.org/jira/browse/HADOOP-6165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom White updated HADOOP-6165:
------------------------------
Attachment: HADOOP-6165-v2.patch
This patch implements 1, and 3.i (for sequence files) above but not 3.ii,
3.iii, or 5. I've changed the accept() method to just take the metadata map,
and not the Class, following Doug's suggestion.
For the 0.21 release it is only necessary to make the API changes to the
serialization framework. This means deprecating the
Serialization/Serializer/Deserializer interfaces and introducing
Base{Serialization,Serializer,Deserializer} (1).
Changes to take full advantage of the new framework in MapReduce (3.ii, 3.iii)
can be introduced progressively in later JIRAs, since they will be additions
and shouldn't affect backward compatibility.
> Add metadata to Serializations
> ------------------------------
>
> Key: HADOOP-6165
> URL: https://issues.apache.org/jira/browse/HADOOP-6165
> Project: Hadoop Common
> Issue Type: New Feature
> Components: contrib/serialization
> Reporter: Tom White
> Priority: Blocker
> Fix For: 0.21.0
>
> Attachments: HADOOP-6165-v2.patch, HADOOP-6165.patch
>
>
> The Serialization framework only allows a class to be passed as metadata.
> This assumes there is a one-to-one mapping between types and Serializations,
> which is overly restrictive. By permitting applications to pass arbitrary
> metadata to Serializations, they can get more control over which
> Serialization is used, and would also allow, for example, one to pass an Avro
> schema to an Avro Serialization.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
