You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ambari.apache.org by "Mingjiang Shi (JIRA)" <ji...@apache.org> on 2014/10/14 10:15:34 UTC

[jira] [Updated] (AMBARI-7770) Allow update the App.defaultStackVersion in config.js to a stack-specific value at build time

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

Mingjiang Shi updated AMBARI-7770:
----------------------------------
    Summary: Allow update the App.defaultStackVersion  in config.js to a stack-specific value at build time  (was: Allow update the App.defaultStackVersion  in config. js to a stack-specific value at build time)

> Allow update the App.defaultStackVersion  in config.js to a stack-specific value at build time
> ----------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-7770
>                 URL: https://issues.apache.org/jira/browse/AMBARI-7770
>             Project: Ambari
>          Issue Type: Improvement
>          Components: ambari-web
>    Affects Versions: 1.7.0
>            Reporter: Mingjiang Shi
>
> In the ambari-web/app/config.js, the App.defaultStackVersion is hardcoded to 'HDP-2.0.5'. This causes a few issues for non-hdp stacks, for example, the services in the Admin tab will not be displayed.
> It would be great if the value can be updated to a stack-specific value (for example, BIGTOP-0.8 for bigtop) at build time by passing some variable. 



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