[
https://issues.apache.org/jira/browse/AMBARI-17358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15359558#comment-15359558
]
Hudson commented on AMBARI-17358:
---------------------------------
FAILURE: Integrated in Ambari-trunk-Commit #5204 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/5204/])
AMBARI-17358. After switching to external database in hive, user should
(hiveww:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=9c7e7615128652b5abb8216946007d59f9a2dced])
* ambari-web/test/models/stack_service_component_test.js
* ambari-web/app/routes/main.js
* ambari-web/test/views/main/host/details/host_component_view_test.js
* ambari-web/app/models/stack_service_component.js
* ambari-web/app/views/main/host/details/host_component_view.js
> After switching to external database in hive, user should be allowed to
> delete mysql server
> -------------------------------------------------------------------------------------------
>
> Key: AMBARI-17358
> URL: https://issues.apache.org/jira/browse/AMBARI-17358
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-web
> Affects Versions: 2.4.0
> Reporter: Anita Gnanamalar Jebaraj
> Assignee: Anita Gnanamalar Jebaraj
> Priority: Minor
> Fix For: 2.4.0
>
> Attachments: AMBARI-17358.patch
>
>
> When user switches from MySQL to Existing database in hive and stop the MySQL
> Server
> 1) Ambari UI > Hive > Service Actions > Stop becomes unavailable, so Hive
> can't be stopped anymore
> 2) Hive status is showing up as red Triangle indicating there is a problem
> with Hive
> Providing an option to delete MySQL server when an existing database is used
> in Hive would help in overcoming the issues.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
