[
https://issues.apache.org/jira/browse/HBASE-1521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Gray reopened HBASE-1521:
----------------------------------
Assignee: Jonathan Gray
This is not a dupe of HBASE-2462. That jira deals with the heuristics for
actually doing a compaction and which files to compact. This jira deals with
what should be processed during a minor compaction (deletes, versions, ttl,
etc).
I'm going to be revisiting this issue in the next few days as part of a new use
case I have where enforcing maxVersions on minors (and possibly even on flush)
would be necessary.
Let's keep open for now and I will either resolve or punt next week.
> Optimize codepath for minor compactions
> ---------------------------------------
>
> Key: HBASE-1521
> URL: https://issues.apache.org/jira/browse/HBASE-1521
> Project: HBase
> Issue Type: Improvement
> Affects Versions: 0.20.0, 0.90.0
> Reporter: Jonathan Gray
> Assignee: Jonathan Gray
> Fix For: 0.90.0
>
>
> There are some additional optimizations in the specialized StoreScanner and
> also in HFile for minor compactions. For example, there is some KV
> disassembling and sanity checking in HFile even though in a minor compaction
> these checks have already been run during the flush.
> Another area to discuss is whether we should actually process deletes during
> minor compactions. It's not especially expensive (ScanDeleteTracker is quite
> simple) but it requires looking at both the row and the qualifier value of
> every single KV. Removing this would drop our axiom that "Deletes only apply
> to later storefiles", which is used during Get processing to have more
> efficient delete handling.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
