[
https://issues.apache.org/jira/browse/HBASE-9036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13718619#comment-13718619
]
Hadoop QA commented on HBASE-9036:
----------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12593973/HBASE-9036-v1-trunk.patch
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 6 new
or modified tests.
{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:green}+1 site{color}. The mvn site goal succeeds with this patch.
{color:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/6453//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6453//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6453//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6453//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6453//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6453//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6453//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6453//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6453//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/6453//console
This message is automatically generated.
> Few small code cleanup
> ----------------------
>
> Key: HBASE-9036
> URL: https://issues.apache.org/jira/browse/HBASE-9036
> Project: HBase
> Issue Type: Bug
> Reporter: Jean-Marc Spaggiari
> Assignee: Jean-Marc Spaggiari
> Priority: Minor
> Fix For: 0.98.0
>
> Attachments: HBASE-9036-v0-trunk.patch, HBASE-9036-v1-trunk.patch
>
>
> Few code cleanup from HBase trunk.
> 1) TestOperation use String.format with 6 %s but give 7 parameters.
> Resolution: Trivial
> 2) ClassFinder can throw a NPE.
> If jarFile = new JarInputStream(new FileInputStream(jarFileName)); throw an
> exception and we want to proceed on exceptions, jarFile will be null, and
> just few lines after we will do a jarFile.getNextJarEntry() where NPE is not
> catch and will fail and throw an NPE. So I thinkg we can't proceed on
> exceptions for this first try since it will fail just the after with an NPE
> and we will loose the information about the real cause of the exception.
> Therefor, we should always throw ioEx is the InputStream creation fails.
> 3)AccessController declare cfs but never use it.
> 4) FavoredNodeAssignmentHelper invokes toString on an array.
> Just changed that to Bytes.toString() to print the server name.
> 5) ModifyTableHandler invokes toString on the tableName array.
> Just changed that to Bytes.toString() to print the table name.
> 6) HFileWriterV2 invokes toString on the keys arrays.
> Just changed that to Bytes.toStringBinary() to print the keys. And change
> some toString() calls to toStringBinary()
> 7) ServerAndLoad want to be serializable, but ServerName is not.
> Made ServerName serializable since it's only Strings, numbers and bytes.
> 8) StorageClusterStatusModel want to be serializable, but its nested class
> Node is not.
> Made Node serializable since it's only numbers and bytes.
> 9) In HRegion outResults can't be null since it's already used for
> outResults.isEmpty() few lines above.
> Just remove the test.
> 10) In RegionScannerHolder region can't be null since it's already used for
> region.startRegionOperation (and others) few lines above.
> Just remove the test.
> 11) CellCounter thisRowFamilyName can't be null since toStringBinary will
> return the string "null" for a null value.
> Just remove the test.
> 12) CellCounter again, thisRowQualifierName can't be null since it's strings
> concatenations.
> Just remove the test.
> 13) HBaseFsck setDisplayFullReport should be static since writing to a static
> field.
--
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
