[
https://issues.apache.org/jira/browse/HBASE-14141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15648714#comment-15648714
]
Vladimir Rodionov edited comment on HBASE-14141 at 11/8/16 9:24 PM:
--------------------------------------------------------------------
Continued.
h5. RegionGroupingProvider, RegionGroupingStrategy API change
Currently both work on encoded region names, where it is impossible to extract
table names from. So we will need to modify API and add table names to
{code}
public WAL getWAL(final byte[] identifier, byte[] namespace)
{code}
calls.
h5. New RegionGroupingStrategy - BackupRegionGroupingStrategy
* There will be a dedicated group for tables in backups.
* It is a wrapper for default or a user specified RegionGroupingStrategy. It
returns backup group name for a table in a backup list (from hbase:backup),
otherwise it calls default strategy
* Group name for backup tables is well known (hardcoded)
h5. Changes to current implementation
h6. All backup operations only on backup sets
Users won't be able to run backup on table or list of tables - only on backup
sets, but users still be able to restore a single table.
h6. Backup set add / remove
After adding/removing table to/from backup set, system disables/enables table
to read new backup set content (for activating/deactivating backup WAL for a
table)
Upd. Instead of direct disable/enable we can implement procedure, which which
updates WAL instance in HRegion (may be tricky)
was (Author: vrodionov):
Continued.
h5. RegionGroupingProvider, RegionGroupingStrategy API change
Currently both work on encoded region names, where it is impossible to extract
table names from. So we will need to modify API and add table names to
{code}
public WAL getWAL(final byte[] identifier, byte[] namespace)
{code}
calls.
h5. New RegionGroupingStrategy - BackupRegionGroupingStrategy
* There will be a dedicated group for tables in backups.
* It is a wrapper for default or a user specified RegionGroupingStrategy. It
returns backup group name for a table in a backup list (from hbase:backup),
otherwise it calls default strategy
* Group name for backup tables is well known (hardcoded)
h5. Changes to current implementation
h6. All backup operations only on backup sets
Users won't be able to run backup on table or list of tables - only on backup
sets, but users still be able to restore a single table.
h6. Backup set add / remove
After adding/removing table to/from backup set, system disables/enables table
to read new backup set content (for activating/deactivating backup WAL for a
table)
> HBase Backup/Restore Phase 3: Filter WALs on backup to include only edits
> from backup tables
> --------------------------------------------------------------------------------------------
>
> Key: HBASE-14141
> URL: https://issues.apache.org/jira/browse/HBASE-14141
> Project: HBase
> Issue Type: New Feature
> Affects Versions: 2.0.0
> Reporter: Vladimir Rodionov
> Assignee: Vladimir Rodionov
> Labels: backup
> Fix For: 2.0.0
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
