[
https://issues.apache.org/jira/browse/HBASE-6428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13418924#comment-13418924
]
Lars Hofhansl commented on HBASE-6428:
--------------------------------------
Another way of looking at this is a possible policy that considers all HFile in
terms of a baseline + changes on top of that baseline.
(For the record: I am not saying that I will do this any time soon, just
recording this as an idea).
> Pluggable Compaction policies
> -----------------------------
>
> Key: HBASE-6428
> URL: https://issues.apache.org/jira/browse/HBASE-6428
> Project: HBase
> Issue Type: New Feature
> Reporter: Lars Hofhansl
>
> For some usecases is useful to allow more control over how KVs get compacted.
> For example one could envision storing old versions of a KV separate HFiles,
> which then rarely have to be touched/cached by queries querying for new data.
> In addition these date ranged HFile can be easily used for backups while
> maintaining historical data.
> This would be a major change, allowing compactions to provide multiple
> targets (not just a filter).
--
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
