hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Taylor (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HBASE-8197) Cannot distinguish between HBase default config value and client overridden config value
Date Tue, 26 Mar 2013 05:09:17 GMT
James Taylor created HBASE-8197:
-----------------------------------

             Summary: Cannot distinguish between HBase default config value and client overridden
config value
                 Key: HBASE-8197
                 URL: https://issues.apache.org/jira/browse/HBASE-8197
             Project: HBase
          Issue Type: Bug
    Affects Versions: 0.94.6
            Reporter: James Taylor
            Priority: Minor


By HBase setting default values in hbase-default.xml, it makes it difficult for a platform
to know if a value has been overridden by the client. For example, Phoenix has a default value
it would like to use for hbase.client.scanner.caching. I'd like to be able to call config.setIfUnset
option to use our default value if a client hasn't already provided their own. Since HBase
sets this in hbase-default.xml to 1, I can't differentiate between the client have a value
in their hbase-sites.xml as 1 versus the default value we're getting from HBase.

Wouldn't it be better if HBase had constants defined in a Java interface that would be used
by HBase as the default value if none other is provided, like this:

    config.getInt("hbase.client.scanner.caching", HBaseDefault.CLIENT_SCANNER_CACHING);



--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message