Return-Path: 
 <issues-return-66815-apmail-hbase-issues-archive=hbase.apache.org@hbase.apache.org>
X-Original-To: apmail-hbase-issues-archive@www.apache.org
Delivered-To: apmail-hbase-issues-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 94FDFD14D
	for <apmail-hbase-issues-archive@www.apache.org>;
 Wed, 31 Oct 2012 00:28:12 +0000 (UTC)
Received: (qmail 15191 invoked by uid 500); 31 Oct 2012 00:28:12 -0000
Delivered-To: apmail-hbase-issues-archive@hbase.apache.org
Received: (qmail 15155 invoked by uid 500); 31 Oct 2012 00:28:12 -0000
Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:issues-help@hbase.apache.org>
List-Unsubscribe: <mailto:issues-unsubscribe@hbase.apache.org>
List-Post: <mailto:issues@hbase.apache.org>
List-Id: <issues.hbase.apache.org>
Delivered-To: mailing list issues@hbase.apache.org
Received: (qmail 15146 invoked by uid 99); 31 Oct 2012 00:28:12 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 31 Oct 2012 00:28:12 +0000
Date: Wed, 31 Oct 2012 00:28:12 +0000 (UTC)
From: "Jonathan Hsieh (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <1127775622.47950.1351643292377.JavaMail.jiratomcat@arcas>
In-Reply-To: <641294419.18550.1341662194634.JavaMail.jiratomcat@issues-vm>
Subject: [jira] [Commented] (HBASE-6353) Snapshots shell
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394


    [ https://issues.apache.org/jira/browse/HBASE-6353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13487401#comment-13487401 ] 

Jonathan Hsieh commented on HBASE-6353:
---------------------------------------

Hey Jesse, I believe this got all +1's on the review.  Can we commit this to the snapshot branch so this isn't hanging around anymore?  

https://reviews.apache.org/r/7583/
                
> Snapshots shell
> ---------------
>
>                 Key: HBASE-6353
>                 URL: https://issues.apache.org/jira/browse/HBASE-6353
>             Project: HBase
>          Issue Type: Sub-task
>          Components: shell
>            Reporter: Matteo Bertozzi
>            Assignee: Matteo Bertozzi
>         Attachments: HBASE-6353-v0.patch
>
>
> h6. hbase shell with snapshot commands
> * snapshot <snapshot name> <table name>
> ** Take a snapshot of the specified name with the specified name 
> * restore_snapshot <snapshot name>
> ** Restore specified snapshot on the original table
> * mount_snapshot <snapshot name> <table name> [readonly]
> ** Load the snapshot data as specified table (optional readonly flag)
> * list_snapshots [filter]
> ** Show a list of snapshots
> * delete_snapshot <snapshot name>
> ** Remove a specified snapshot
> h6. Restore Table
> Given a "snapshot name" restore override the original table with the snapshot content.
> Before restoring a new snapshot of the table is taken, just to avoid bad situations.
> (If the table is not disabled we can keep serving reads)
> This allows a full and quick rollback to a previous snapshot.
> h6. Mount Table (Aka Clone Table)
> Given a "snapshot name" a new table is created with the content of the specified snapshot.
> This operation allows:
>  * To have an old version of the table in parallel with the current one.
>  ** Look at snapshot side-by-side with the "current" before making the decision whether to roll back or not
>  * To Restore only "individual items" (only some small range of data was lost from "current")
>  ** MR job that scan the cloned table and update the data in the original one. (Partial restore of the data)
>  * if the table is not marked as read-only
>  ** To Add/Remove data from this table without affecting the original one or the snapshot.
> h6. Open points
>  * Add snapshot type option on take snapshot command (global, timestamp)?
>  * Keep separate the "restore" from "mount"?

--
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