You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Anoop Sam John (JIRA)" <ji...@apache.org> on 2018/01/04 10:15:00 UTC

[jira] [Commented] (HBASE-19664) MOB should compatible with other types of Compactor in addition to DefaultCompactor

    [ https://issues.apache.org/jira/browse/HBASE-19664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16311116#comment-16311116 ] 

Anoop Sam John commented on HBASE-19664:
----------------------------------------

This is a real concern.. 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.. The inclusion of MOB flush/compaction still need a smoother approach to make sure other features can be used together with.  [~dujingch@gmail.com] what do u think boss?  

> 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)