[
https://issues.apache.org/jira/browse/HBASE-15988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15364855#comment-15364855
]
Vladimir Rodionov commented on HBASE-15988:
-------------------------------------------
Hmm.
Suppose you have table set of 150 tables and all of them are OK (with full
backup), you add new one, which does not have backup yet. Next time you run
incremental backup on this set, the backup will be converted to FULL for all
151 tables, or to FULL for only 1(?). I do not think user expects either one.
When we add new tables to a backup set, we need to 3 conditions:
# all tables have backups - nothing to do
# all tables do not have backups - nothing to do
# some have, some do not - trigger FULL backup for tables which do not have
backups yet or throw exception ("Can not add ..., run FULL backup first for
tables ...). This can be configurable, say *-force* will trigger full backup
automatically.
> Backup set add command MUST initiate full backup for a table(s) being added
> ---------------------------------------------------------------------------
>
> Key: HBASE-15988
> URL: https://issues.apache.org/jira/browse/HBASE-15988
> Project: HBase
> Issue Type: Task
> Affects Versions: 2.0.0
> Reporter: Vladimir Rodionov
> Labels: backup
> Fix For: 2.0.0
>
> Attachments: 15988.v1.txt, 15988.v2.txt
>
>
> When a new table is added to backup table set, the incremental backup
> involving the new table should be full backup.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
