[
https://issues.apache.org/jira/browse/HBASE-12859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14277957#comment-14277957
]
Lars Hofhansl commented on HBASE-12859:
---------------------------------------
We can use that for:
* Implement predicate based deletes, where this would solve the problem of
knowing when we can let go of the predicate ([~larsgeorge])
* For transactions where we need to keep track rolled back transactions, and
know where we can let go of old transaction ids ([~ghelmling])
* And probably a bunch of other things.
Determining the last compaction time would involve a scan of META, but that
should be OK.
> Major compaction completion tracker
> -----------------------------------
>
> Key: HBASE-12859
> URL: https://issues.apache.org/jira/browse/HBASE-12859
> Project: HBase
> Issue Type: Brainstorming
> Reporter: Lars Hofhansl
>
> In various scenarios it is helpful to know a guaranteed timestamp up to which
> all data in a table was major compacted.
> We can do that keeping a major compaction timestamp in META.
> A client then can iterate all region of a table and find a definite
> timestamp, which is the oldest compaction timestamp of any of the regions.
> [~apurtell], [~ghelmling], [~giacomotaylor].
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
