You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2018/04/05 16:57:00 UTC
[jira] [Commented] (HBASE-16656) BackupID must include backup set
name
[ https://issues.apache.org/jira/browse/HBASE-16656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16427249#comment-16427249 ]
stack commented on HBASE-16656:
-------------------------------
FYI, I've stripped 2.0.0 as fixVersion from all these backup issues resolved against 2.0.0 (they are not in 2.0.0). [~vrodionov] and [~yuzhihong@gmail.com] Thanks.
> BackupID must include backup set name
> -------------------------------------
>
> Key: HBASE-16656
> URL: https://issues.apache.org/jira/browse/HBASE-16656
> Project: HBase
> Issue Type: Sub-task
> Reporter: Vladimir Rodionov
> Assignee: Vladimir Rodionov
> Priority: Major
> Labels: backup
> Fix For: 2.0.0
>
> Attachments: HBASE-16656-v1.patch, HBASE-16656-v2.patch, HBASE-16656-v3.patch, HBASE-16656-v4.patch
>
>
> Default backup set name is "backup". If we do backup for a backup set "SomeSetName", by default, backup id will be generated in a form:
> *SomeSetName_timestamp*.
> The goal is to separate backup images between different sets.
> The history command will be updated and the new command - merge will use this backup names (prefixes)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)