[jira] [Commented] (AMBARI-5437) ServiceComponent metadata on the web-client should not be deleted if Stack doesn't support Service

["Yusaku Sako (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AMBARI-5437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13966147#comment-13966147 ] 

Yusaku Sako commented on AMBARI-5437:
-------------------------------------

+1 for the patch.

> ServiceComponent metadata on the web-client should not be deleted if Stack doesn't support Service 
> ---------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-5437
>                 URL: https://issues.apache.org/jira/browse/AMBARI-5437
>             Project: Ambari
>          Issue Type: Bug
>          Components: client
>    Affects Versions: 1.6.0
>            Reporter: Jaimin D Jetly
>            Assignee: Jaimin D Jetly
>             Fix For: 1.6.0
>
>         Attachments: AMBARI-5437.patch
>
>
> On getting service components information for the selected stack from the server, web-client goes through all the config categories defined in data/service_config.js. Config categories are mapped to serviceComponents. If there is a serviceComponent defined over here but the serviceComponent is not defined in the stack then we delete all the metadata for the serviceComponent (configCategory in data/service_configs.js, properties in data/global_properties and data/review_configs). 
> This deletion should not be done if the above condition holds true while service is not part of the stack. If the service is not the part of the stack then we anyways hide all the information related to the service on all pages. so web-client can work without deleting them



--
This message was sent by Atlassian JIRA
(v6.2#6252)