[
https://issues.apache.org/jira/browse/HBASE-15862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15322676#comment-15322676
]
Carter Shanklin commented on HBASE-15862:
-----------------------------------------
Wanted to give my thoughts, the question here is specifically around whether
the -overwrite should or should not truncate the tables in the table set before
restoring. To me as a user I would expect it to do the truncation automatically
because I said -overwrite, this is a destructive operation and I accept this as
a user. As I look at some of the comments I'm not sure if Jerry agrees or not,
the DB2 behavior seems consistent with automatically truncating.
Having the user manually delete the tables:
1. Makes me switch to a different tool (the HBase Ruby shell as opposed the
backup commands)
2. When we get to backup/restore for Phoenix, automatic truncation will have
several advantages, such as not breaking or forcing re-creation of secondary
indexes.
So why force users to take that extra step?
> Backup - Delete- Restore does not restore deleted data
> ------------------------------------------------------
>
> Key: HBASE-15862
> URL: https://issues.apache.org/jira/browse/HBASE-15862
> Project: HBase
> Issue Type: Bug
> Affects Versions: 2.0.0
> Reporter: Vladimir Rodionov
> Assignee: Vladimir Rodionov
> Labels: backup
> Fix For: 2.0.0
>
> Attachments: HBASE-15862-v1.patch
>
>
> This was discovered during testing. If we delete row after full backup and
> perform immediately restore, the deleted row still remains deleted.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
