[
https://issues.apache.org/jira/browse/HADOOP-6698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12859601#action_12859601
]
Hadoop QA commented on HADOOP-6698:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12442493/HADOOP-6698.patch
against trunk revision 936463.
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 15 new or modified tests.
-1 javadoc. The javadoc tool appears to have generated 1 warning messages.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
-1 findbugs. The patch appears to introduce 2 new Findbugs warnings.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
+1 core tests. The patch passed core unit tests.
+1 contrib tests. The patch passed contrib unit tests.
Test results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h4.grid.sp2.yahoo.net/472/testReport/
Findbugs warnings:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h4.grid.sp2.yahoo.net/472/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h4.grid.sp2.yahoo.net/472/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h4.grid.sp2.yahoo.net/472/console
This message is automatically generated.
> Revert the io.serialization package to 0.20.2's api
> ---------------------------------------------------
>
> Key: HADOOP-6698
> URL: https://issues.apache.org/jira/browse/HADOOP-6698
> Project: Hadoop Common
> Issue Type: Bug
> Components: io
> Reporter: Owen O'Malley
> Priority: Blocker
> Fix For: 0.21.0
>
> Attachments: HADOOP-6698.patch
>
>
> I have a lot of concern about the usability of the new generic serialization
> framework. Toward that end, I've filed a jira for improving it. There is
> resistance to pushing a new API into 0.21 at the last moment, so we should
> back out the changes rather than introducing a new api in 0.21 and
> deprecating it in 0.22.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
