ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Di Li (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (AMBARI-15719) Make list of reassignable components stack driven instead of hardcoding them in the UI code
Date Thu, 07 Apr 2016 21:53:25 GMT

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

Di Li reassigned AMBARI-15719:
------------------------------

    Assignee: Di Li

> Make list of reassignable components stack driven instead of hardcoding them in the UI
code
> -------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-15719
>                 URL: https://issues.apache.org/jira/browse/AMBARI-15719
>             Project: Ambari
>          Issue Type: Improvement
>          Components: ambari-server, ambari-web
>    Affects Versions: trunk
>            Reporter: Di Li
>            Assignee: Di Li
>             Fix For: trunk
>
>         Attachments: AMBARI-15719.patch
>
>
> When a component is reassignable, the Ambari web UI adds the "Move" menu item to the
component menu on the host page.
> The logic on whether a component should be displayed with the "Move" menu item is currently
controlled by the following hardcoded list.
> /** @property {Boolean} isReassignable - component supports reassign action **/
>   isReassignable: function() {
>     return ['NAMENODE', 'SECONDARY_NAMENODE', 'JOBTRACKER', 'RESOURCEMANAGER', 'APP_TIMELINE_SERVER',
'OOZIE_SERVER', 'WEBHCAT_SERVER', 'HIVE_SERVER', 'HIVE_METASTORE', 'MYSQL_SERVER', 'METRICS_COLLECTOR'].contains(this.get('componentName'));
>   }.property('componentName'),
> We should make the list stack driven by specify whether a component is reassignable via
a flag in the metainfo.xml.



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

Mime
View raw message