ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-13084) Ambari UI issues in SAPHD builds
Date Mon, 14 Sep 2015 12:18:45 GMT

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

Hudson commented on AMBARI-13084:
---------------------------------

FAILURE: Integrated in Ambari-trunk-Commit #3436 (See [https://builds.apache.org/job/Ambari-trunk-Commit/3436/])
AMBARI-13084 Ambari UI issues in SAPHD builds.  (ababiichuk) (ababiichuk: http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=63dded51d90d06f1ca7e55e6b756a5343c22659e)
* ambari-web/app/data/HDP2/site_properties.js
* ambari-web/app/data/HDP2.3/site_properties.js
* ambari-web/app/views/common/controls_view.js
* ambari-web/app/messages.js


> Ambari UI issues in SAPHD builds
> --------------------------------
>
>                 Key: AMBARI-13084
>                 URL: https://issues.apache.org/jira/browse/AMBARI-13084
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-web
>    Affects Versions: 2.1.2
>            Reporter: Andrii Babiichuk
>            Assignee: Andrii Babiichuk
>            Priority: Critical
>             Fix For: 2.1.2
>
>         Attachments: AMBARI-13084.patch
>
>
> 1. We should NOT show SQLAnywhere as an option for any builds except for SAP; show SQLAnywhere
as an option if the stack name is SAPHD.
> 2. SQLAnywhere requires HDP 2.3.2 or greater message, therefore, does not make sense.
Let's get rid of that.



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

Mime
View raw message