[
https://issues.apache.org/jira/browse/HBASE-3909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13487432#comment-13487432
]
Subbu M Iyer commented on HBASE-3909:
-------------------------------------
call to containsKey(). If null is returned from get(), we delegate to
super.get(). This applies to getLong(), etc.
This is tricky. Basically my thought is it's quite possible that some one
has overridden a configuration key with null value explicitly and in such
cases we do not want to override the same with default value from config.
So, if the key is present in CHM, then we must use it no matter what the
value is.
thoughts ?
On Mon, Oct 29, 2012 at 10:12 AM, Ted Yu (JIRA) <j...@apache.org> wrote:
> Add dynamic config
> ------------------
>
> Key: HBASE-3909
> URL: https://issues.apache.org/jira/browse/HBASE-3909
> Project: HBase
> Issue Type: Bug
> Reporter: stack
> Assignee: Subbu M Iyer
> Fix For: 0.96.0
>
> Attachments: 3909_090712-2.patch, 3909-102812.patch,
> 3909-102912.patch, 3909.v1, 3909-v1.patch, HBase Cluster Config Details.xlsx,
> patch-v2.patch, testMasterNoCluster.stack
>
>
> I'm sure this issue exists already, at least as part of the discussion around
> making online schema edits possible, but no hard this having its own issue.
> Ted started a conversation on this topic up on dev and Todd suggested we
> lookd at how Hadoop did it over in HADOOP-7001
--
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
