[jira] [Updated] (HBASE-7360) Snapshot 0.94 Backport

["Lars Hofhansl (JIRA)" <ji...@apache.org>]

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

Lars Hofhansl updated HBASE-7360:
---------------------------------

    Fix Version/s: 0.94.7

Putting 0.94.7 as a placeholder for now.

I assume that both Cloudera and Hortonworks are still interested in backporting the patch, making it a defacto standard...?

In order to get this into 0.94 I would suggest the following:
# Cloudera and Hortonworks work together and agree on a *single* patch.
# That patch would be carefully tested by both companies.
# The testing includes passing all unittests (naturally) as well as tests in physical clusters of reasonable size.
# The patch can be delivered as one large patch, or as a series of smaller patches (whatever turns out to be less work).

Does that make sense?
                
> Snapshot 0.94 Backport 
> -----------------------
>
>                 Key: HBASE-7360
>                 URL: https://issues.apache.org/jira/browse/HBASE-7360
>             Project: HBase
>          Issue Type: New Feature
>          Components: snapshots
>    Affects Versions: 0.94.3
>            Reporter: Matteo Bertozzi
>            Assignee: Matteo Bertozzi
>             Fix For: 0.94.7
>
>
> Backport snapshot code to 0.94
> The main changes needed to backport the snapshot are related to the protobuf vs writable rpc.
> Offline Snapshot
>  * HBASE-6610 - HFileLink: Hardlink alternative for snapshot restore
>  * HBASE-6765 - Take a Snapshot interface
>  * HBASE-6571 - Generic multi-thread/cross-process error handling framework
>  * HBASE-6353 - Snapshots shell
>  * HBASE-7107 - Snapshot References Utils (FileSystem Visitor)
>  * HBASE-6863 - Offline snapshots
>  * HBASE-6865 - Snapshot File Cleaners
>  * HBASE-6777 - Snapshot Restore Interface
>  * HBASE-6230 - Clone/Restore Snapshots
>  * HBASE-6802 - Export Snapshot

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira