[
https://issues.apache.org/jira/browse/HBASE-6427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13423679#comment-13423679
]
Lars Hofhansl edited comment on HBASE-6427 at 7/27/12 5:11 AM:
---------------------------------------------------------------
v3... Fixes some things, and verifies the new scenarios.
Still not quite done, yet, just need a place to "park" it.
preStoreScannerOpen will be called for Gets (which is good), including internal
Gets (or append/increment/delete/etc). I *think* this is OK in all cases, but
need to make sure.
Edit: Spelling
was (Author: lhofhansl):
v3... Fixes some things, and verifies the new scenarios.
Still not quite done, yet, just need a place to "park" it.
preStoreScannerOpen will be called for Gets (which is good), including internal
Gets (or append/increment/delete/etc. I *think* this is OK in all cases, by
need to make sure.
> 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
> Assignee: Lars Hofhansl
> Priority: Minor
> Attachments: 6427-notReady.txt, 6427-v1.txt, 6427-v2.txt, 6427-v3.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
