[
https://issues.apache.org/jira/browse/AMBARI-9459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14304142#comment-14304142
]
Hudson commented on AMBARI-9459:
--------------------------------
SUCCESS: Integrated in Ambari-trunk-Commit #1679 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/1679/])
AMBARI-9459. Remove oozie-server item from +Add button on host page if oozie db
is derby (alexantonenko) (hiveww:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=373ff1137e8c0352181f9a603ac14500218ccd6c)
* ambari-web/app/routes/main.js
* ambari-web/app/views/main/host/summary.js
* ambari-web/app/controllers/main/host/details.js
> Remove oozie-server item from +Add button on host page if oozie db is derby
> ---------------------------------------------------------------------------
>
> Key: AMBARI-9459
> URL: https://issues.apache.org/jira/browse/AMBARI-9459
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
> Affects Versions: 2.0.0
> Reporter: Antonenko Alexander
> Assignee: Antonenko Alexander
> Fix For: 2.0.0
>
> Attachments: AMBARI-9459.patch
>
>
> After i've changed cardinality for oozie server to 1+, we can add this
> component using +Add button on host page. But, this ability should be
> available only if oozie using existing db, not derby.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
