You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Vladimir Rodionov (JIRA)" <ji...@apache.org> on 2018/01/02 23:10:00 UTC

[jira] [Commented] (HBASE-19568) Restore of HBase table using incremental backup doesn't restore rows from an earlier incremental backup

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

Vladimir Rodionov commented on HBASE-19568:
-------------------------------------------

{quote}
How about passing in the Configuration instead of creating a new one? You have one in restoreImages already.
{quote}

That is conf for local cluster, won't work.

> Restore of HBase table using incremental backup doesn't restore rows from an earlier incremental backup
> -------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-19568
>                 URL: https://issues.apache.org/jira/browse/HBASE-19568
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Romil Choksi
>            Assignee: Vladimir Rodionov
>         Attachments: HBASE-19568-v1.patch
>
>
> Credits to [~romil.choksi]
> Restore of bulk-loaded HBase table doesn't restore deleted rows
> Steps:
> Create usertable and insert a few rows in it
> Create full backup
> Bulk load into usertable, and create first incremental backup
> Bulk load into usertable again, and create second incremental backup
> Delete row each from initial insert, first bulk load and second bulk load
> Restore usertable using second incremental backup
> Verify if each of the deleted rows has been restored
> On restore using second incremental backup id, the test failed as all of the rows from first bulk load were not available. Data from initial insertion (full backup) and second bulk load were only available.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)