You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-dev@hadoop.apache.org by "Owen O'Malley (JIRA)" <ji...@apache.org> on 2009/04/04 01:24:12 UTC

[jira] Updated: (HADOOP-5450) Add support for application-specific typecodes to typed bytes

     [ https://issues.apache.org/jira/browse/HADOOP-5450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Owen O'Malley updated HADOOP-5450:
----------------------------------

      Resolution: Fixed
    Hadoop Flags: [Reviewed]
          Status: Resolved  (was: Patch Available)

I just committed this. Thanks, Klaas!

> Add support for application-specific typecodes to typed bytes
> -------------------------------------------------------------
>
>                 Key: HADOOP-5450
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5450
>             Project: Hadoop Core
>          Issue Type: Improvement
>          Components: contrib/streaming
>            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.
-
You can reply to this email to add a comment to the issue online.