ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-16158) takeover_config_merge.py should process known template config files
Date Thu, 28 Apr 2016 18:55:13 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-16158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15262725#comment-15262725
] 

Hudson commented on AMBARI-16158:
---------------------------------

FAILURE: Integrated in Ambari-trunk-Commit #4758 (See [https://builds.apache.org/job/Ambari-trunk-Commit/4758/])
AMBARI-16158. takeover_config_merge.py should process known template (aonishuk: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=e1069651db0f503f15c8b31ec50f1932d65ab7be])
* ambari-server/src/main/resources/scripts/takeover_config_merge.py


> takeover_config_merge.py should process known template config files
> -------------------------------------------------------------------
>
>                 Key: AMBARI-16158
>                 URL: https://issues.apache.org/jira/browse/AMBARI-16158
>             Project: Ambari
>          Issue Type: Bug
>            Reporter: Andrew Onischuk
>            Assignee: Andrew Onischuk
>             Fix For: 2.4.0
>
>         Attachments: AMBARI-16158.patch
>
>
> `/var/lib/ambari-server/resources/scripts/takeover_config_merge.py` currently
> only processes XML content files (*-site.xml, etc.). However there are a lot
> of other files which need to end up managed by Ambari.
> At a minimum this script should load in the known template type files (*-env,
> *-log4j, etc.). Also, it should take care of capacity-scheduler configs.
> Not processing these files will result in too much effort for users into
> getting their content, removing new lines, and making them JSON compliant - to
> keep into the blueprint.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message