[
https://issues.apache.org/jira/browse/HBASE-8385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13636909#comment-13636909
]
Matteo Bertozzi commented on HBASE-8385:
----------------------------------------
this was a design decision...
for me restore and clone are the same operation... but we divided that...
restore means that you're restoring on something that exists
clone means that you're creating a new table from nothing.
There's this check in HBaseAdmin.restoreSnapshot()
{code}
if (tableName == null) {
throw new RestoreSnapshotException(
"Unable to find the table name for snapshot=" + snapshotName);
}
{code}
> [SNAPSHOTS]: Restore fails to restore snapshot of a deleted table
> -----------------------------------------------------------------
>
> Key: HBASE-8385
> URL: https://issues.apache.org/jira/browse/HBASE-8385
> Project: HBase
> Issue Type: Bug
> Components: snapshots
> Affects Versions: 0.98.0, 0.94.7, 0.95.1, 0.95.2
> Reporter: Aleksandr Shulman
> Assignee: Aleksandr Shulman
> Fix For: 0.98.0, 0.94.7, 0.95.1, 0.95.2
>
> Attachments: HBASE-8385-test-v1.patch
>
>
> Expected behavior:
> A user should be able to:
> 1. Take a snapshot of a table
> 2. Delete that table
> 3. Use the snapshot to restore that deleted table
> Observed behavior:
> During a restore, we attempt to create a snapshot of the table should the
> restore go awry. However, the snapshot fails because the table that we want
> to snapshot is not present.
--
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
