[
https://issues.apache.org/jira/browse/HBASE-15862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15323573#comment-15323573
]
Vladimir Rodionov commented on HBASE-15862:
-------------------------------------------
Schema evolution and its support is on the roadmap - HBASE-15449.
We have 3 options:
# Restore to a current schema (truncate approach)
# Restore to a schema of a last full backup (delete approach)
# Restore to a schema of a backup being restored (PIT schema- HBASE-15448).
No. 3 is right one, but its in Phase 3. For now we can use either #1 or #2. I
prefer #1, because, in most cases, the most recent schema (region splits) will
be much closer to our PIT, than schema (region splits) of a last full backup.
I vote for #1 (current patch), just we have to clarify that until we get
HBASE-15448(9) *we do not support physical layout change of a table*.
> 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, HBASE-15862-v2.patch,
> HBASE-15862-v3.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)
