Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Date: Fri, 9 Mar 2012 21:14:59 +0000 (UTC)
From: "Arun C Murthy (Commented) (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: 
 <815257677.45562.1331327699733.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HADOOP-5450) Add support for
 application-specific typecodes to typed bytes
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HADOOP-5450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13226465#comment-13226465 ] 

Arun C Murthy commented on HADOOP-5450:
---------------------------------------

Matt - Klaas's patch applies clean to branch-1. I'd like to push it in for hadoop-1.0.2, you ok? Thanks.
                
> Add support for application-specific typecodes to typed bytes
> -------------------------------------------------------------
>
>                 Key: HADOOP-5450
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5450
>             Project: Hadoop Common
>          Issue Type: Improvement
>            Reporter: Klaas Bosteels
>            Assignee: Klaas Bosteels
>            Priority: Blocker
>             Fix For: 0.21.0
>
>         Attachments: HADOOP-5450.patch
>
>
> For serializing objects of types that are not supported by typed bytes serialization, applications might want to use a custom serialization format. Right now, typecode 0 has to be used for the bytes resulting from this custom serialization, which could lead to problems when deserializing the objects because the application cannot know if a byte sequence following typecode 0 is a customly serialized object or just a raw sequence of bytes. Therefore, a range of typecodes that are treated as aliases for 0 should be added, such that different typecodes can be used for application-specific purposes.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira