You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Vladimir Rodionov (JIRA)" <ji...@apache.org> on 2016/07/05 18:50:11 UTC

[jira] [Resolved] (HBASE-14416) HBase Backup/Restore Phase 3: Create plugin hooks for Backup tools

     [ https://issues.apache.org/jira/browse/HBASE-14416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vladimir Rodionov resolved HBASE-14416.
---------------------------------------
    Resolution: Won't Fix

We have already HBaseBackupAdmin API. Different  backup implementation can provide its own BackupAdmin.

> HBase Backup/Restore Phase 3: Create plugin hooks for Backup tools
> ------------------------------------------------------------------
>
>                 Key: HBASE-14416
>                 URL: https://issues.apache.org/jira/browse/HBASE-14416
>             Project: HBase
>          Issue Type: New Feature
>    Affects Versions: 2.0.0
>            Reporter: Geoffrey Jacoby
>              Labels: backup
>             Fix For: 2.0.0
>
>
> Different organizations may already have their own backup tools for HBase, or wish to develop them in the future for their own particular use cases. It would be useful if HBase supported hooks to integrate those tools so that they could be configured and run in a standard way.
> In particular, the administrative interface to start a backup, restore, or merge should be decoupled from any particular implementation as much as possible, so that any implementation with similar capabilities can be substituted via configuration without needing to fork or modify the code. 
> Ideally, it will also be possible to decouple the various components so that implementations can be mixed and matched. (For example, one could use the standard backup's functionality to track what needs to be backed up, but use a custom plugin to change the logic or storage format of the backup operation itself.)



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