hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ramkrishna.s.vasudevan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-17333) HBASE-17294 always ensures CompactingMemstore is default
Date Mon, 19 Dec 2016 07:19:58 GMT

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

ramkrishna.s.vasudevan commented on HBASE-17333:
------------------------------------------------

bq.The way to enable compacting Memstore now is to config the type as basic/eager.
I still feel if there is CompactingMemstore (and one needs it) then it should be either Basic/Eager
and one among this should be default. So having default type as NONE is not right in this
context.


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

Mime
View raw message