[ https://issues.apache.org/jira/browse/HBASE-4522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118312#comment-13118312 ]
Mikhail Bautin commented on HBASE-4522: --------------------------------------- Discussed this with Liyin. To clarify Liyin's point above: in our setup, we have multiple clusters per application, and hbase-site.xml works as the application-specific configuration, while hbase-site-custom.xml is the cluster-specific configuration within a particular application. So in our case hbase-site.xml does not hard-code any host names. The reason we cannot use hbase-default.xml for application-specific configuration is that there is already an hbase-default.xml file in the HBase jar, and overriding it would make us dependent on the relative ordering of HBase configuration directory and the HBase jar in the classpath, which is an unnecessarily brittle approach. With the hbase-site-custom.xml file, however, we get additional flexibility in configuring our HBase clusters without breaking backwards-compatibility. If the hbase-site-custom.xml file is not there, everything will function exactly as before. > 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