[
https://issues.apache.org/jira/browse/HBASE-6427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13423384#comment-13423384
]
Lars Hofhansl commented on HBASE-6427:
--------------------------------------
Of course this has to be compared to simply making the ScanInfo pluggable in
Store.java.
What I want to achieve here is to have an external process (backup tool,
transaction engine, etc) to be able to override HBase's default TTL/#Versions
with very high fidelity (i.e. not via a dynamic schema change, which is too
heavyweight/slow).
The coprocessor approach is nice, because it provides a lot of flexibility for
other future use cases and it does not invent a new concept. At the same time
it adds complexity.
> Pluggable compaction policies via coprocessors
> ----------------------------------------------
>
> Key: HBASE-6427
> URL: https://issues.apache.org/jira/browse/HBASE-6427
> Project: HBase
> Issue Type: New Feature
> Reporter: Lars Hofhansl
> Priority: Minor
> Attachments: 6427-notReady.txt, 6427-v1.txt
>
>
> 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
