[
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-v4.patch
bq. Since AvroGenericSerialization is added last, the fallback could simply be
to change its accept method to accept anything that has AVRO_SCHEMA_KEY
defined, no?
Done.
bq. One other thing: we should probably adopt a naming convention for metadata
keys. Should they be Java-package-like strings, e.g.,
org.apache.hadoop.io.serialization.class, or HTTP/SMTP header-like things,
e.g., Serialization-Class?
In this case I don't have a strong feeling either way, so I've changed the keys
to be named as "header-like things".
> 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
> Assignee: Tom White
> Priority: Blocker
> Fix For: 0.21.0
>
> Attachments: HADOOP-6165-v2.patch, HADOOP-6165-v3.patch,
> HADOOP-6165-v4.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.
