[
https://issues.apache.org/jira/browse/HBASE-17333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15760402#comment-15760402
]
Anoop Sam John commented on HBASE-17333:
----------------------------------------
bq.COMPACTING_MEMSTORE_ENABLED = "hbase.hregion.compacting.memstore";
Why new config? I think in other issue, Eschar removed other configs and
tuning points and went with single type config.. Now why we need this?
The way to enable compacting Memstore now is to config the type as basic/eager.
> HBASE-17294 always ensures CompactingMemstore is default
> --------------------------------------------------------
>
> Key: HBASE-17333
> URL: https://issues.apache.org/jira/browse/HBASE-17333
> Project: HBase
> Issue Type: Bug
> Reporter: ramkrishna.s.vasudevan
> Assignee: ramkrishna.s.vasudevan
> Priority: Critical
> Fix For: 2.0.0
>
> Attachments: HBASE-17333.patch, HBASE-17333_1.patch
>
>
> Was the purpose of HBASE-17294 is to make Compacting Memstore as default? Am
> not sure on that. But that patch makes DefaultMemstore as a Noop. This JIRA
> is to discuss and revert back to default memstore only if the family is not
> configured for in memory flush/compaction.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
