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 "Klaas Bosteels (JIRA)" <ji...@apache.org> on 2009/03/10 16:28:51 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 ]
Klaas Bosteels updated HADOOP-5450:
-----------------------------------
Attachment: HADOOP-5450.patch
The attached patch makes sure that the typecode range 50-200 can be used for application-specific purposes. As an example, it also makes {{TypedBytesWritableInput}} and {{TypedBytesWritableOutput}} use typecode 50 for serializing Writables that do not match with any of the types supported by the typed bytes format.
> 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
> 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.