hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tom White (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-6165) Add metadata to Serializations
Date Fri, 14 Aug 2009 15:20:14 GMT

     [ 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-v3.patch

Here's a new patch which adopts the names suggested by Doug. I've also added AvroGenericSerialization
which looks for a schema in the metadata, and a test for it. I haven't added the fallback
capability discussed, but it shouldn't be too hard to add.

I've also fixing failing tests, and reduced the number of deprecation warnings - I can't get
rid of all of them until the deprecated interfaces are removed.

> 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.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.

View raw message