[
https://issues.apache.org/jira/browse/HBASE-6427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13422394#comment-13422394
]
Lars Hofhansl commented on HBASE-6427:
--------------------------------------
The other scenario where this is useful is for M/R based incremental backups
(as described here:
http://hadoop-hbase.blogspot.com/2012/04/timestamp-consistent-backups-in-hbase.html).
The backup tools can then control exactly what data to keep, while the backups
are running.
The actual plugged policy would probably coordinate via ZK.
> Pluggable policy for smallestReadPoint in HRegion
> -------------------------------------------------
>
> Key: HBASE-6427
> URL: https://issues.apache.org/jira/browse/HBASE-6427
> Project: HBase
> Issue Type: New Feature
> Reporter: Lars Hofhansl
> Priority: Minor
>
> When implementing higher level stores on top of HBase it is necessary to
> allow dynamic control over how long KVs must be kept around.
> Semi-static config options for ColumnFamilies (# of version or TTL) is not
> sufficient.
> The simplest way to achieve this is to have a pluggable class to determine
> the smallestReadpoint for Region. That way outside code can control what KVs
> to retain.
--
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
