hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-6353) Snapshots shell
Date Tue, 06 Nov 2012 22:04:13 GMT

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

Hadoop QA commented on HBASE-6353:

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include any new or modified
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    {color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/3236//console

This message is automatically generated.
> 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, HBASE-6353-v1.patch, snapshot-offline-test-demo.shell
> 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
> * clone_snapshot <snapshot name> <table name>
> ** Create a new table based on the snapshot content
> * list_snapshots [filter]
> ** Show the list of snapshots taken
> * delete_snapshot <snapshot name>
> ** Remove a specified snapshot
> * rename_snapshot <snapshot name> <new snapshot name>
> ** Rename a snapshot to a new name
> 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.
> This allows a full and quick rollback to a previous snapshot.
> h6. Clone from Snapshot
> 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 Add/Remove data from this table without affecting the original one or the snapshot.
>  * 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)
> h6. Open points
>  * Add snapshot type option on take snapshot command (global, timestamp)?

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

View raw message