Jeff Sposetti created AMBARI-5802:
-------------------------------------
Summary: 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: client
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
{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.2#6252)
