[
https://issues.apache.org/jira/browse/HBASE-14302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14710435#comment-14710435
]
Hadoop QA commented on HBASE-14302:
-----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12752094/hbase-14302_v1.patch
against master branch at commit d0873f5a8cc060adbc5a1ae0ed52b84a8942a868.
ATTACHMENT ID: 12752094
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 9 new
or modified tests.
{color:green}+1 hadoop versions{color}. The patch compiles with all
supported hadoop versions (2.4.0 2.4.1 2.5.0 2.5.1 2.5.2 2.6.0 2.7.0)
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 protoc{color}. The applied patch does not increase the
total number of protoc compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 checkstyle{color}. The applied patch does not increase the
total number of checkstyle errors
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) 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 post-site goal
to fail.
{color:red}-1 core tests{color}. The patch failed these unit tests:
org.apache.hadoop.hbase.mapreduce.TestImportExport
org.apache.hadoop.hbase.util.TestProcessBasedCluster
{color:red}-1 core zombie tests{color}. There are 1 zombie test(s):
at
org.apache.giraph.rexster.io.formats.TestRexsterLongDoubleFloatIOFormat.testDbOutput(TestRexsterLongDoubleFloatIOFormat.java:226)
at
org.apache.giraph.rexster.io.formats.TestRexsterLongDoubleFloatIOFormat.testOrientDbOutput(TestRexsterLongDoubleFloatIOFormat.java:154)
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/15230//testReport/
Release Findbugs (version 2.0.3) warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/15230//artifact/patchprocess/newFindbugsWarnings.html
Checkstyle Errors:
https://builds.apache.org/job/PreCommit-HBASE-Build/15230//artifact/patchprocess/checkstyle-aggregate.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/15230//console
This message is automatically generated.
> TableSnapshotInputFormat should not create back references when restoring
> snapshot
> ----------------------------------------------------------------------------------
>
> Key: HBASE-14302
> URL: https://issues.apache.org/jira/browse/HBASE-14302
> Project: HBase
> Issue Type: Bug
> Reporter: Enis Soztutar
> Assignee: Enis Soztutar
> Fix For: 2.0.0, 1.2.0, 1.3.0, 1.0.3, 1.1.3
>
> Attachments: hbase-14302_v1.patch
>
>
> TableSnapshotInputFormat restores the snapshot to a temporary directory that
> is outside the HBase's root directory so that it can read from the restored
> snapshot and also refer to hfiles in the actual root directory.
> In restoring the snapshot, we create new hfilelinks in the ephemeral
> location. Creating new hfile links also creates "back references" for GC.
> These back references are dangling since the restore location is outside the
> root dir, and requires a WRITE permission to the root dir (as opposed to just
> READ permission) to be able to run the MR-over-snapshot job.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
