[ 
https://issues.apache.org/jira/browse/HBASE-7145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13536307#comment-13536307
 ] 

Hadoop QA commented on HBASE-7145:
----------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12561748/7145-trunk-v4.txt
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

    {color:green}+1 tests included{color}.  The patch appears to include 3 new 
or modified tests.

    {color:green}+1 hadoop2.0{color}.  The patch compiles against the hadoop 
2.0 profile.

    {color:green}+1 javadoc{color}.  The javadoc tool did not generate any 
warning messages.

    {color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

    {color:red}-1 findbugs{color}.  The patch appears to introduce 28 new 
Findbugs (version 1.3.9) warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in .

     {color:red}-1 core zombie tests{color}.  There are zombie tests. See build 
logs for details.

Test results: 
https://builds.apache.org/job/PreCommit-HBASE-Build/3615//testReport/
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/3615//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/3615//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/3615//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/3615//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/3615//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/3615//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/3615//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output: 
https://builds.apache.org/job/PreCommit-HBASE-Build/3615//console

This message is automatically generated.
                
> ReusableStreamGzipCodec NPE upon reset with IBM JDK
> ---------------------------------------------------
>
>                 Key: HBASE-7145
>                 URL: https://issues.apache.org/jira/browse/HBASE-7145
>             Project: HBase
>          Issue Type: Sub-task
>    Affects Versions: 0.94.0
>            Reporter: Yu Li
>            Assignee: Yu Li
>              Labels: gzip, ibm-jdk
>             Fix For: 0.96.0
>
>         Attachments: 7145-trunk-v3.txt, 7145-trunk-v4.txt, 7145-trunk-v5.txt, 
> HBASE-7145.1.patch.txt, HBASE-7145.2_trunk.patch.txt
>
>
> This is the same issue as described in HADOOP-8419, repeat the issue 
> description here:
> The ReusableStreamGzipCodec will NPE upon reset after finish when the native 
> zlib codec is not loaded. When the native zlib is loaded the codec creates a 
> CompressorOutputStream that doesn't have the problem, otherwise, the 
> ReusableStreamGzipCodec uses GZIPOutputStream which is extended to provide 
> the resetState method. Since IBM JDK 6 SR9 FP2 including the current JDK 6 
> SR10, GZIPOutputStream#finish will release the underlying deflater(calls the 
> deflater's end method), which causes NPE upon reset. This seems to be an IBM 
> JDK quirk as Sun JDK and OpenJDK doesn't have this issue.
> Since in HBASE-5387 HBase source has refactor its code not to use hadoop's 
> GzipCodec during real compress/decompress, it's necessary to make a separate 
> patch for HBase on the same issue

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to