You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Antonenko Alexander (JIRA)" <ji...@apache.org> on 2015/04/16 20:34:58 UTC

[jira] [Updated] (AMBARI-10544) Views: FE work for adding the ability for a view instance to be associated to a cluster for configuration

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

Antonenko Alexander updated AMBARI-10544:
-----------------------------------------
    Attachment: AMBARI-10544.patch

> Views: FE work for adding the ability for a view instance to be associated to a cluster for configuration
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-10544
>                 URL: https://issues.apache.org/jira/browse/AMBARI-10544
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-web
>    Affects Versions: 2.1.0
>            Reporter: Antonenko Alexander
>            Assignee: Antonenko Alexander
>            Priority: Critical
>             Fix For: 2.1.0
>
>         Attachments: AMBARI-10544.patch
>
>
> One change is that "Configuration" section should be called "Cluster Configuration" in the View Create / Edit page.
> See https://issues.apache.org/jira/browse/AMBARI-10306 for API.
> When querying the "view version" resource, if "clusterConfig" attribute exists for the parameter, then it needs to go into the "Cluster Configuration" section.  Otherwise, the parameter needs to go into the "Settings" section.
> If there are no parameters with the attribute "clusterConfig", then do not show "Cluster Configuration" section in the UI.
> Also, Locally Managed Ambari Server option or the Custom option is "either or".  When Locally Managed is selected, Custom option as well as the parameters should be disabled and vice versa.



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