[
https://issues.apache.org/jira/browse/HBASE-9820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13804338#comment-13804338
]
Hadoop QA commented on HBASE-9820:
----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12610091/HBASE-9820-v0-trunk.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 hadoop1.0{color}. The patch compiles against the hadoop
1.0 profile.
{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:green}+1 findbugs{color}. The patch does not introduce any 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 lineLengths{color}. The patch does not introduce lines
longer than 100
{color:red}-1 site{color}. The patch appears to cause mvn site goal to
fail.
{color:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/7615//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7615//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7615//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7615//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7615//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7615//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7615//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7615//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7615//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-thrift.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7615//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/7615//console
This message is automatically generated.
> Method Replication.decorateMasterConfiguration can fail with NPE in case that
> property HBASE_MASTER_LOGCLEANER_PLUGINS is not defined
> -------------------------------------------------------------------------------------------------------------------------------------
>
> Key: HBASE-9820
> URL: https://issues.apache.org/jira/browse/HBASE-9820
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.96.0
> Reporter: Jarek Jarcec Cecho
> Assignee: Jean-Marc Spaggiari
> Attachments: HBASE-9820-v0-trunk.patch
>
>
> While upgrading HBase dependency on Pig via PIG-3529, I've noticed that
> method {{Replication.decorateMasterConfiguration()}} can throw
> {{NullPointerException}}
> ([code|https://github.com/apache/hbase/blob/0.96/hbase-server/src/main/java/org/apache/hadoop/hbase/replication/regionserver/Replication.java])
> in case when property HBASE_MASTER_LOGCLEANER_PLUGINS won't be defined.
> The issue was more on a pig side where we weren't propagating default HBase
> configuration resources (such as {{hbase-default.xml}}), but I was curious if
> it's expected that this property will be always defined? We might want to
> tweak the code a bit if this property can be null.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
