[
https://issues.apache.org/jira/browse/HBASE-50?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12878411#action_12878411
]
stack commented on HBASE-50:
----------------------------
.bq What if the table with the same name is still online when we want to
restore a snapshot
Fail with a warning. A nice-to-have would be your suggestion of restoring
snapshot into a table named something other than the original table's name
(Fixing this issue is low-priority IMO).
There a few things in the above that make me want to go over the design again.
I'll report back after I've done that. Specifically:
.bq Rename 'reference' family in .META. to 'snapshot'
... didn't we discuss that .META. might not be the place to keep snapshot data
since regions are deleted when the system is done w/ them (but a snapshot may
outlive a particular region).
> Snapshot of table
> -----------------
>
> Key: HBASE-50
> URL: https://issues.apache.org/jira/browse/HBASE-50
> Project: HBase
> Issue Type: New Feature
> Reporter: Billy Pearson
> Assignee: Li Chongxin
> Priority: Minor
> Attachments: HBase Snapshot Design Report V2.pdf, HBase Snapshot
> Design Report V3.pdf, snapshot-src.zip
>
>
> Havening an option to take a snapshot of a table would be vary useful in
> production.
> What I would like to see this option do is do a merge of all the data into
> one or more files stored in the same folder on the dfs. This way we could
> save data in case of a software bug in hadoop or user code.
> The other advantage would be to be able to export a table to multi locations.
> Say I had a read_only table that must be online. I could take a snapshot of
> it when needed and export it to a separate data center and have it loaded
> there and then i would have it online at multi data centers for load
> balancing and failover.
> I understand that hadoop takes the need out of havening backup to protect
> from failed servers, but this does not protect use from software bugs that
> might delete or alter data in ways we did not plan. We should have a way we
> can roll back a dataset.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
