[
https://issues.apache.org/jira/browse/HBASE-10115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13845724#comment-13845724
]
Jean-Marc Spaggiari commented on HBASE-10115:
---------------------------------------------
Hi [~apurtell], how will you build a schema for that?
Like, let's take this usecase.
User push data into HBase with versions=10. And want to make sure data after 10
versions is not lost. They can of course run MR jobs, count the versions, and
make sure that version 10 is stored somewhere else in case a new version is
coming and pushing it out, but will be a pain. Why can't they just hook on this
deletion to do what they want with the version which is going to be purged? I'm
not sure how a schema option can help with that.
> Add a hook for compaction deletes
> ---------------------------------
>
> Key: HBASE-10115
> URL: https://issues.apache.org/jira/browse/HBASE-10115
> Project: HBase
> Issue Type: Bug
> Components: Compaction, Coprocessors
> Affects Versions: 0.99.0
> Reporter: Jean-Marc Spaggiari
> Priority: Minor
>
> The idea is to add a hook to coprocessors to be able to get triggered when
> compaction delete a cell before of the number of versions or the TTL.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
