ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Antonenko Alexander (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-17358) After switching to external database in hive, user should be allowed to delete mysql server
Date Fri, 01 Jul 2016 16:47:11 GMT

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

Antonenko Alexander updated AMBARI-17358:
-----------------------------------------
    Fix Version/s:     (was: trunk)
                   2.4.0

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

Mime
View raw message