[
https://issues.apache.org/jira/browse/HADOOP-5450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12680747#action_12680747
]
Hadoop QA commented on HADOOP-5450:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12401846/HADOOP-5450.patch
against trunk revision 752292.
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 3 new or modified tests.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
+1 findbugs. The patch does not introduce any new Findbugs warnings.
+1 Eclipse classpath. The patch retains Eclipse classpath integrity.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
-1 core tests. The patch failed core unit tests.
+1 contrib tests. The patch passed contrib unit tests.
Test results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-minerva.apache.org/46/testReport/
Findbugs warnings:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-minerva.apache.org/46/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-minerva.apache.org/46/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-minerva.apache.org/46/console
This message is automatically generated.
> 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.
