[jira] [Updated] (AMBARI-17358) After switching to external database in hive, user should be allowed to delete mysql server

["Antonenko Alexander (JIRA)" <ji...@apache.org>]

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

Antonenko Alexander updated AMBARI-17358:
-----------------------------------------
    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

Committed to trunk and 2.4


> 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: trunk
>
>         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)