[
https://issues.apache.org/jira/browse/HBASE-4522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118341#comment-13118341
]
Todd Lipcon commented on HBASE-4522:
------------------------------------
We do configuration management here using puppet. Other deploys I"m aware of
use Chef or bcfg2.
It's not that I think the feature is risky, really... it just feels like bloat
and yet another thing to document. Do any other organizations find this feature
useful?
A more general solution that I'd support would be to support something like
"hbase/conf.d" where any XML files in that directory would be sorted by name,
and loaded in that order. So you could have 01-site.xml, 02-myapplication.xml,
03-my-machine-overrides.xml, etc. This is a more familiar construct for most
sysadmins.
> Make hbase-site-custom.xml override the hbase-site.xml
> ------------------------------------------------------
>
> Key: HBASE-4522
> URL: https://issues.apache.org/jira/browse/HBASE-4522
> Project: HBase
> Issue Type: Improvement
> Reporter: Mikhail Bautin
> Assignee: Liyin Tang
> Priority: Minor
> Fix For: 0.94.0
>
>
> The motivation for diff is that we want to override some config change for
> any specific cluster easily by just adding the config entries in the
> hbase-site-custom.xml for that cluster. This change adds the
> hbase-site-custom.xml configuration file into HBaseConfiguration.
--
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
