ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeff Sposetti (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (AMBARI-5802) Ability to manage -env.sh files for each service
Date Thu, 30 Oct 2014 18:42:34 GMT

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

Jeff Sposetti resolved AMBARI-5802.
-----------------------------------
    Resolution: Duplicate

> Ability to manage -env.sh files for each service
> ------------------------------------------------
>
>                 Key: AMBARI-5802
>                 URL: https://issues.apache.org/jira/browse/AMBARI-5802
>             Project: Ambari
>          Issue Type: Improvement
>          Components: ambari-web
>    Affects Versions: 1.6.0
>            Reporter: Jeff Sposetti
>
> Expose in Ambari (REST API and Web UI) the ability to manage the -env.sh files associated
with each Service in a Stack.
> For example, here is the list from HDP 2.1 Stack:
> {code}
> HDFS > hadoop-env.sh
> YARN > yarn-env.sh
> MapReduce2 > mapred-env.sh
> Hive > hive-env.sh
> Hive > hcat-env.sh
> WebHCat > webhcat-env.sh
> Oozie > oozie-env.sh
> Sqoop > sqoop-env.sh
> ZooKeeper > zookeeper-env.sh
> Pig > pig-env.sh
> HBase > hbase-env.sh
> Tez > tez-env.sh
> Falcon > falcon-env.sh
> Storm > storm-env.sh
> {code}
> Currently, these are all managed as j2 templates. When these get added to a Service definition
as a configuration type, the user should be able to manage the template itself.



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

Mime
View raw message