[
https://issues.apache.org/jira/browse/AMBARI-25456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Szabolcs Beki updated AMBARI-25456:
-----------------------------------
Description:
The epic would make it possible for Ambari admins to include their own custom
config in the standard config file in Hadoop core-site.xml. Adding a line like
this in the beginning of the file
{code:java}
<configuration xmlns:xi="http://www.w3.org/2001/XInclude";>
<xi:include href="/tmp/customInputDataConfig.xml" />
{code}
Currently Ambari handles this config file as set of keys and parameters and
rewrites on each ambari restart overwriting any such inclusions.
was:
The epic would make it possible for Ambari admins to include their own custom
config in the standard config file in Hadoop core-site.xml. Adding a line like
this in the beginning of the file
{code:java}
<configuration xmlns:xi="http://www.w3.org/2001/XInclude";>
<xi:include href="/tmp/customInputDataConfig.xml" />
{code}
{{}}{{}}{{}}
Currently Ambari handles this config file as set of keys and parameters and
rewrites on each ambari restart overwriting any such inclusions.
> Include Custom Config file via Ambari
> -------------------------------------
>
> Key: AMBARI-25456
> URL: https://issues.apache.org/jira/browse/AMBARI-25456
> Project: Ambari
> Issue Type: Epic
> Components: ambari-agent, ambari-server, ambari-web
> Reporter: Szabolcs Beki
> Priority: Minor
>
> The epic would make it possible for Ambari admins to include their own custom
> config in the standard config file in Hadoop core-site.xml. Adding a line
> like this in the beginning of the file
>
> {code:java}
> <configuration xmlns:xi="http://www.w3.org/2001/XInclude";>
> <xi:include href="/tmp/customInputDataConfig.xml" />
> {code}
>
> Currently Ambari handles this config file as set of keys and parameters and
> rewrites on each ambari restart overwriting any such inclusions.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
