hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rekha Joshi (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (HBASE-10711) Savepoint, Rollback features on Hbase Shell and API
Date Mon, 10 Mar 2014 08:47:43 GMT

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

Rekha Joshi reassigned HBASE-10711:
-----------------------------------

    Assignee: Rekha Joshi

> Savepoint, Rollback features on Hbase Shell and API
> ---------------------------------------------------
>
>                 Key: HBASE-10711
>                 URL: https://issues.apache.org/jira/browse/HBASE-10711
>             Project: HBase
>          Issue Type: New Feature
>          Components: Admin, shell
>    Affects Versions: 0.94.17
>            Reporter: Rekha Joshi
>            Assignee: Rekha Joshi
>
> In parallel to SQLWorld, Hbase needs to have easy feature to savepoint/rollback/commit.
> This functionality can help retrieve table state before a set of commands are executed.Especially
if one inadvertently drops a table, rollback is a lifesaver.
> SAVEPOINT < savepoint_name >;
> ROLLBACK [TO SAVEPOINT < savepoint_name>];
> COMMIT;
> This internally will take a snapshot of table(s) when a command 'savepoint' is executed
on hbase shell/api.Each savepoint takes the snapshot , and stores the map with savepoint id
to snapshot taken.Will need a retrieval from the last-est savepoint id.
> Given that it might take some time, this savepoint is the users option if one is into
too many operations and one operation goes wrong, they can still start from save point.For
better perf, it would be nice to provide command set tables 'a','b','c' and the savepoint
command then takes the snapshots of only those tables rather than all.
> Maybe i am a burnt child dreading the fire, but thoughts?



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message