[ 
https://issues.apache.org/jira/browse/HBASE-19568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Rodionov updated HBASE-19568:
--------------------------------------
    Description: 
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.


> 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: Vladimir Rodionov
>            Assignee: Vladimir Rodionov
>
> 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)

Reply via email to