[
https://issues.apache.org/jira/browse/HBASE-1521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12719320#action_12719320
]
Erik Holstad commented on HBASE-1521:
-------------------------------------
I totally agree with Jonathan on this one, even though we are the once that
have tried to optimize the get path. Having a fast compact and is more
important,
in my opinion. The one case where it will make the biggest slowdown is the case
when getting stuff from memcache, which is already one of the fastest, so
feels like a good place to make the system more even. And since we don't even
are sure about the future of the get implementation I think it is more important
to focus on other parts like compaction speed.
> Optimize codepath for minor compactions
> ---------------------------------------
>
> Key: HBASE-1521
> URL: https://issues.apache.org/jira/browse/HBASE-1521
> Project: Hadoop HBase
> Issue Type: Improvement
> Affects Versions: 0.20.0
> Reporter: Jonathan Gray
> Fix For: 0.20.1
>
>
> 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.
