[
https://issues.apache.org/jira/browse/HBASE-7290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13531133#comment-13531133
]
Jonathan Hsieh commented on HBASE-7290:
---------------------------------------
When I say 'restore' in step 4, I am specifically referring to a 'snapshot
restore' operation. It doesn't necessarily have to happen after a crash.
Suppose a user creates data, snapshots it, then puts bad data in. The use
wants the old data back so he restores the snapshot (there is no crash anywhere
here).
While what you suggest is true, (they could restore again), this is unexpected,
even in our weaker consistency model. If we have a table, have a crash and
come back we essentially expect the table to be essentially the same as before.
(without potentially tons of new data appear.
> Online snapshots
> -----------------
>
> Key: HBASE-7290
> URL: https://issues.apache.org/jira/browse/HBASE-7290
> Project: HBase
> Issue Type: Bug
> Reporter: Jonathan Hsieh
>
> HBASE-6055 will be closed when the offline snapshots pieces get merged with
> trunk. This umbrella issue has all the online snapshot specific patches.
> This will get merged once one of the implementations makes it into trunk.
> Other flavors of online snapshots can then be done as normal patches instead
> of on a development branch.
--
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
