[
https://issues.apache.org/jira/browse/HBASE-14272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14732464#comment-14732464
]
Lars Hofhansl commented on HBASE-14272:
---------------------------------------
Yep... Unless there's MIN_VERSIONS :)
0.94 unconditionally re-compacted files for time-based major compactions, we
need to make we do not accidentally revert back to that.
The simplest by far would be to simply to simply disable this optimization when
the CF has TTL or hbase.hstore.time.to.purge.deletes is > 0. Those are the only
two settings that have a time-component, i.e. where the set of visible Cell
will change over time.
We can rule out hbase.hstore.time.to.purge.deletes by tracking whether there
are delete markers left in the HFile (which would fail if KEEP_DELETED_CELLS is
set).
> Enforce major compaction on stores with KEEP_DELETED_CELLS=true
> ---------------------------------------------------------------
>
> Key: HBASE-14272
> URL: https://issues.apache.org/jira/browse/HBASE-14272
> Project: HBase
> Issue Type: Bug
> Reporter: Vladimir Rodionov
> Assignee: Vladimir Rodionov
> Fix For: 2.0.0
>
> Attachments: HBASE-14272-v2.patch, HBASE-14272.patch
>
>
> Currently, if store has one (major compacted) file, the only case when major
> compaction will be triggered for this file again - when locality is below
> threshold, defined by *hbase.hstore.min.locality.to.skip.major.compact* or
> TTL expired some cells. If file has locality greater than this threshold it
> will never be major compacted until Store's TTL kicks in. For CF with
> KEEP_DELETED_CELLS on, compaction must be enabled always (even for single
> file), regardless of locality, when deleted cells are expired
> (*hbase.hstore.time.to.purge.deletes*)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
