[
https://issues.apache.org/jira/browse/HBASE-6055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13293482#comment-13293482
]
Lars Hofhansl commented on HBASE-6055:
--------------------------------------
Let's try to avoid going overboard here.
In principle snapshot and backup/restore are different and independent.
A snapshot generates a consistent snapshot of the data that can subsequently be
copied conveniently somewhere else - thus creating a backup.
Ideally we would not even prescribe the backup/restore semantics here, but just
provide missing building blocks.
Just my $0.02.
Another thought here is: In principle an HFile resulting from a major
compaction could be considered a baseline copy and additional HFiles would be
incremental changes on top of that baseline. It might be worth considering if
we can make use of this ability of HBase to overlay changes from many sources
into a single view of the data (would probably be tricky as regions are flushed
in sync, etc, just waving hands here).
> Snapshots in HBase 0.96
> -----------------------
>
> Key: HBASE-6055
> URL: https://issues.apache.org/jira/browse/HBASE-6055
> Project: HBase
> Issue Type: New Feature
> Components: client, master, regionserver, zookeeper
> Reporter: Jesse Yates
> Assignee: Jesse Yates
> Fix For: 0.96.0
>
> Attachments: Snapshots in HBase.docx
>
>
> Continuation of HBASE-50 for the current trunk. Since the implementation has
> drastically changed, opening as a new ticket.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
