Jaimin D Jetly created AMBARI-6959:
--------------------------------------
Summary: Stacks service API: Need for a separate config dependency
field.
Key: AMBARI-6959
URL: https://issues.apache.org/jira/browse/AMBARI-6959
Project: Ambari
Issue Type: Task
Components: site
Affects Versions: 1.7.0
Reporter: Jaimin D Jetly
Assignee: Andrew Onischuk
Priority: Critical
Fix For: 1.7.0
Right now service metainfo definition provides
configuration-dependencies tag that is exposed in the API as configTypes field.
API should expose two different fields:
*1. configTypesDependencies:*
Name of all the configuration types on which the service is dependent. UI will
use this for *service restart required functionality*. NOTE: This can be more
than the configuration carried by the service. Example Hive service does not
expose tez-site configs but requires restart when tez-configs change.
*2. configTypes:*
Name of all the configuration types that the service carries in it's
configuration folder. UI will use this to *display configType section and
configurations on the service config page*.
As of now UI Uses the configTypes files that actually gives configDependencies
values by hard-coding the references to the services in the web-code which can
lead to potential bugs when service metainfo.xml is changed with to address
just one functionality
--
This message was sent by Atlassian JIRA
(v6.2#6252)
