hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-6610) HFileLink: Hardlink alternative for snapshot restore
Date Fri, 28 Sep 2012 06:35:08 GMT

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

Hadoop QA commented on HBASE-6610:
----------------------------------

-1 overall.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12546963/6610v9.patch
  against trunk revision .

    +1 @author.  The patch does not contain any @author tags.

    +1 tests included.  The patch appears to include 11 new or modified tests.

    -1 patch.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/2957//console

This message is automatically generated.
                
> HFileLink: Hardlink alternative for snapshot restore
> ----------------------------------------------------
>
>                 Key: HBASE-6610
>                 URL: https://issues.apache.org/jira/browse/HBASE-6610
>             Project: HBase
>          Issue Type: Sub-task
>          Components: io
>    Affects Versions: 0.96.0
>            Reporter: Matteo Bertozzi
>            Assignee: Matteo Bertozzi
>              Labels: snapshot
>             Fix For: 0.96.0
>
>         Attachments: 6610v9.patch, HBASE-6610-v1.patch, HBASE-6610-v2.patch, HBASE-6610-v3.patch,
HBASE-6610-v5.patch, HBASE-6610-v6.patch, HBASE-6610-v7.patch, HBASE-6610-v8.patch
>
>
> To avoid copying data during restore snapshot we need to introduce an HFile Link  that
allows to reference a file that can be in the original path (/hbase/table/region/cf/hfile)
or, if the file is archived, in the archive directory (/hbase/.archive/table/region/cf/hfile).

--
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

Mime
View raw message