[
https://issues.apache.org/jira/browse/HADOOP-5450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arun C Murthy updated HADOOP-5450:
----------------------------------
Fix Version/s: 1.0.2
Thanks Matt. I've committed to branch-1 after running tests.
> 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, 1.0.2
>
> 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
