hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Purtell (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-12660) Sanity check other loadable classes from configuration
Date Tue, 09 Dec 2014 02:11:12 GMT

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

Andrew Purtell commented on HBASE-12660:

bq. For example "hbase.hstore.engine.class".

As the code stands today, we can check the store engine class loadability but we can't check
what it wants wrt. compactor, flusher, or compaction policy without instantiating it (because
how it determines which class to select is entirely implementation dependent), and we can't
do that without creating a real Store object, because some store components want in their
constructors a Store object for getting configuration. I suppose when the master role is colocated
with regionserver roles that's not so bad. And/or we could spend some time on making sure
we can create instances of configurable plugin classes and check their health prior to creating
an active store. 

> Sanity check other loadable classes from configuration
> ------------------------------------------------------
>                 Key: HBASE-12660
>                 URL: https://issues.apache.org/jira/browse/HBASE-12660
>             Project: HBase
>          Issue Type: Sub-task
>            Reporter: Enis Soztutar
> As per parent, we do a sanity check for compression, region split policy, coprocessors
and encryption. 
> We should add more checks for the other classes that can be configured (either at the
RS level or table / CF level). For example "hbase.hstore.engine.class". 

This message was sent by Atlassian JIRA

View raw message