[
https://issues.apache.org/jira/browse/HBASE-3909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13294735#comment-13294735
]
Subbu M Iyer commented on HBASE-3909:
-------------------------------------
I have tried to capture all (most of) of configuration properties that are
currently being used in an excel.
The objective here is to figure out what properties may be effectively changed
using the dynamic config utility and what is not. While doing this exercise I
figured that almost close to 200 properties are missing from hbase-default.xml
but is getting used in the system.
So, here are my thoughts on this and would like to hear from you guys your
thoughts as well:
1. My understanding is that all configuration properties will be/must be
defined in hbase-default.xml with a default value. Some exceptions are possible
in some corner cases but majority of properties must be defined here.
2. There is no way for a user to know that a property is
configurable/changeable unless 1) the property is defined in hbase-default 2)
Or communicated through some documentation or API doc.
> Add dynamic config
> ------------------
>
> Key: HBASE-3909
> URL: https://issues.apache.org/jira/browse/HBASE-3909
> Project: HBase
> Issue Type: Bug
> Reporter: stack
> Fix For: 0.96.0
>
> Attachments: 3909-v1.patch, 3909.v1
>
>
> 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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
