[
https://issues.apache.org/jira/browse/HBASE-4522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118334#comment-13118334
]
Mikhail Bautin commented on HBASE-4522:
---------------------------------------
@Todd: if I understand correctly, template-based configuration management means
you generate configuration files using an external site-specific tool. As far
as I see, there is no standardized tool like that so far in the HBase user
community (could you please point it out to me if I'm wrong?) Our approach
does not require an external template system (it only relies on
copying/symlinking the right files into the conf directory) and provides a
clearer separation of between application-specific and site-specific
configuration. The "feature" in this JIRA is around two lines of code and does
not break existing functionality while providing additional flexibility. That
said, it would be very interesting to hear about alternative approaches to
Hadoop/HBase configuration management for large multi-cluster deployments --
please feel free to share.
> 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
