[
https://issues.apache.org/jira/browse/HBASE-4867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phabricator updated HBASE-4867:
-------------------------------
Attachment: D537.1.patch
mbautin requested code review of "[jira] [HBASE-4867] A tool to merge
configuration files".
Reviewers: todd, Karthik, tedyu, stack, JIRA
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.
REVISION DETAIL
https://reviews.facebook.net/D537
AFFECTED FILES
src/main/python/hbase/merge_conf.py
MANAGE HERALD DIFFERENTIAL RULES
https://reviews.facebook.net/herald/view/differential/
WHY DID I GET THIS EMAIL?
https://reviews.facebook.net/herald/transcript/1191/
Tip: use the X-Herald-Rules header to filter Herald messages in your client.
> 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
>
>
> 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
