[
https://issues.apache.org/jira/browse/HBASE-8199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13614301#comment-13614301
]
Hadoop QA commented on HBASE-8199:
----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12575529/HBASE-8199-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 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:red}-1 core tests{color}. The patch failed these unit tests:
org.apache.hadoop.hbase.master.TestAssignmentManagerOnCluster
org.apache.hadoop.hbase.master.TestTableLockManager
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/5021//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5021//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5021//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5021//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5021//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5021//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5021//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5021//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5021//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/5021//console
This message is automatically generated.
> Eliminate exception for ExportSnapshot against the null table snapshot (with
> no data in)
> ----------------------------------------------------------------------------------------
>
> Key: HBASE-8199
> URL: https://issues.apache.org/jira/browse/HBASE-8199
> Project: HBase
> Issue Type: Improvement
> Components: snapshots
> Affects Versions: 0.95.0, 0.94.6, 0.94.7
> Reporter: Julian Zhou
> Assignee: Julian Zhou
> Priority: Minor
> Fix For: 0.95.0, 0.94.6
>
> Attachments: HBASE-8199-0.94.patch, HBASE-8199-trunk.patch
>
>
> In the test environment, when snapshoting the null table (with no data),
> snapshot artifact can be generated successfully with snapshot meta data,
> while there is no CF data under region dir. Then when exporting this null
> snapshot via ExportSnapshot, "java.io.IOException: No input paths specified
> in job" occurred, which affects the normal application flow.
> But seems snapshot for null table also makes sense just with the meta
> information (.snapshot/), although ".archive/" does not show up. Later
> snapshot restore seems work from this "dummy" snapshot artifact with no CF
> data.
> Just eliminate exception for ExportSnapshot against the null table snapshot
> to make application work through.
--
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
