[
https://issues.apache.org/jira/browse/HBASE-6427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lars Hofhansl updated HBASE-6427:
---------------------------------
Attachment: 6427-notReady.txt
Here's an initial idea for a patch.
For this to work coprocessors need to have access to KeyValueScanner,
StoreScanner, etc. So that is violating/leaking some of the previous
abstractions.
This patch would allow a coprocessor to actually produce a scanner for a flush
or a compaction, while not requiring it to reimplement all the logic.
A coprocessor can now in fact just override the TTL and/or # versions for a
flush/compaction.
Please let me know what you think and how to improve this.
And for the love of god, please think of better names for the two new hooks.
> 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
> Attachments: 6427-notReady.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
