[
https://issues.apache.org/jira/browse/HBASE-4867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13160694#comment-13160694
]
Hudson commented on HBASE-4867:
-------------------------------
Integrated in HBase-TRUNK-security #17 (See
[https://builds.apache.org/job/HBase-TRUNK-security/17/])
[jira] [HBASE-4867] A tool to merge configuration files
Summary: With our cluster configuration setup it would be good to have a tool
that would merge HBase configuration files so that files appearing later in the
list would override properties specified in earlier files. This way we could
merge an application-specific configuration file with a cluster-specific
configuration file (with the latter overriding the former) and produce a single
HBase configuration file to install on the cluster.
Test Plan: Run the tool on two configuration files (common and
cluster-specific). Use the resulting configuration on a dev cluster.
Reviewers: todd, Karthik, tedyu, stack, JIRA
Reviewed By: Karthik
CC: Karthik, mbautin, todd
Differential Revision: 537
karthik :
Files :
* /hbase/trunk/src/main/python
* /hbase/trunk/src/main/python/hbase
* /hbase/trunk/src/main/python/hbase/merge_conf.py
> A tool to merge configuration files
> -----------------------------------
>
> Key: HBASE-4867
> URL: https://issues.apache.org/jira/browse/HBASE-4867
> Project: HBase
> Issue Type: New Feature
> Reporter: Mikhail Bautin
> Assignee: Mikhail Bautin
> Priority: Minor
> Attachments: D537.1.patch, D537.2.patch, D537.3.patch
>
>
> With our cluster configuration setup it would be good to have a tool that
> would merge HBase configuration, so that files appearing later in the list
> would override properties specified in earlier files. This way we could merge
> application-specific configuration file with the cluster-specific
> configuration file (with the latter overriding the former) and produce a
> single HBase configuration file to install on the cluster.
--
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
