hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jerry He (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-15449) HBase Backup Phase 3: Support physical table layout change
Date Sat, 27 Aug 2016 00:03:21 GMT

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

Jerry He commented on HBASE-15449:
----------------------------------

Ok.  Is this a optimization/short-cut of the normal sequence of restores?  This only works
if the user specifies auto restore and specifies the last PIT image to restore to?
Does it work if user does one restore at a time manual restore?  Does it work for incremental
restore WAL replay?

The LoadIncrementalHFiles change can be done in a separate JIRA for general use?

> HBase Backup Phase 3: Support physical table layout change 
> -----------------------------------------------------------
>
>                 Key: HBASE-15449
>                 URL: https://issues.apache.org/jira/browse/HBASE-15449
>             Project: HBase
>          Issue Type: Task
>    Affects Versions: 2.0.0
>            Reporter: Vladimir Rodionov
>            Assignee: Vladimir Rodionov
>              Labels: backup
>             Fix For: 2.0.0
>
>         Attachments: 15449.v1.txt, 15449.v2.txt, 15449.v4.txt, 15449.v5.txt
>
>
> Table operation such as add column family, delete column family, truncate , delete table
may result in subsequent backup restore failure.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message