[
https://issues.apache.org/jira/browse/HBASE-3909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13295267#comment-13295267
]
stack commented on HBASE-3909:
------------------------------
bq. 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.
IMO, on #1 in your first of two comments above Subbu, there are configs. that
are do not have to be in hbase-default. Such configs. are those we think we'd
never change but that we've made configurable just-in-case. This class of
config can only be found by reading source code. We don't add them to
hbase-default.xml because they detract from the important configs. in the flat
hbase-default xml file (Maybe this is less of an issue now we 'hide'
hbase-default.xml inside the jar and the book includes description). If we do
add these to hbase-default.xml, I'd think we'd add an annotation saying like
'exotic' or 'not-for-the-faint-of-heart').
On #2, I think its fine that they have to read the source for esoterics.
On your second set of comments, I think yes, this is an important feature to
have and I agree many configs. will not be changeable without extensive
refactoring server-side (and even then, some may be just plain dangerous to
change in mid-flight). Perhaps we do a subset in this case and if you stray
outside of the subset, you get an exception.
> 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, HBase Cluster Config
> Details.xlsx, patch-v2.patch
>
>
> 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
