[
https://issues.apache.org/jira/browse/HBASE-19664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16311193#comment-16311193
]
chenxu edited comment on HBASE-19664 at 1/4/18 11:16 AM:
---------------------------------------------------------
bq. Though am not fully convinced by the approach of removing the own classes
for MOB and adding instance checks and both kinds of methods in one place..
yes, that's not a perfect approach, move up performMobFlush and
performMobCompaction to super class in order to reuse them when there is a new
Compactor impl
was (Author: javaman_chen):
bg.Though am not fully convinced by the approach of removing the own classes
for MOB and adding instance checks and both kinds of methods in one place..
yes, that's not a perfect approach, move up performMobFlush and
performMobCompaction to super class in order to reuse them when there is a new
Compactor impl
> MOB should compatible with other types of Compactor in addition to
> DefaultCompactor
> -----------------------------------------------------------------------------------
>
> Key: HBASE-19664
> URL: https://issues.apache.org/jira/browse/HBASE-19664
> Project: HBase
> Issue Type: Improvement
> Components: mob
> Reporter: chenxu
> Attachments: HBASE-19664-master-v1.patch
>
>
> Currently when MOB feature enabled, we will use MobStoreEngine to deal with
> flush and compaction, but it extends DefaultStoreEngine, so the stripe
> compaction feature can not be used.
> In some scenes, Stripe Compaction are very useful, it can reduce the number
> of regions and prevent a single storefile grow too large，If it
> compatible with MOB feature, that’s perfect.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
