You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Andrew Onischuk (JIRA)" <ji...@apache.org> on 2016/04/28 15:55:13 UTC

[jira] [Updated] (AMBARI-16158) takeover_config_merge.py should process known template config files

     [ https://issues.apache.org/jira/browse/AMBARI-16158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Onischuk updated AMBARI-16158:
-------------------------------------
    Attachment: AMBARI-16158.patch

> 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)