hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Umesh Agashe (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (HBASE-19161) For system tables, if config 'hbase.systemtables.compacting.memstore.type' is not specified then DefaultMemStore is used
Date Fri, 03 Nov 2017 04:29:00 GMT

     [ https://issues.apache.org/jira/browse/HBASE-19161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Umesh Agashe resolved HBASE-19161.
----------------------------------
    Resolution: Won't Fix

> For system tables, if config 'hbase.systemtables.compacting.memstore.type' is not specified
then DefaultMemStore is used
> ------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-19161
>                 URL: https://issues.apache.org/jira/browse/HBASE-19161
>             Project: HBase
>          Issue Type: Bug
>          Components: regionserver
>    Affects Versions: 2.0.0-alpha-4
>            Reporter: Umesh Agashe
>            Assignee: Umesh Agashe
>            Priority: Minor
>             Fix For: 2.0.0-beta-1
>
>
> For system tables, if config 'hbase.systemtables.compacting.memstore.type' is not specified
then code default 'NONE' is used which causes instantiation of DefaultMemStore class. That
means for everyone to use  CompactingMemStore they need to specify this config value. Reversing
it will help i.e. if user explicitly specifies 'hbase.systemtables.compacting.memstore.type'
to 'NONE' then only DefaultMemStore class is used.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message