[jira] [Commented] (AMBARI-17358) After switching to external database in hive, user should be allowed to delete mysql server
[ https://issues.apache.org/jira/browse/AMBARI-17358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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=commit=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)
[jira] [Commented] (AMBARI-17358) After switching to external database in hive, user should be allowed to delete mysql server
[
https://issues.apache.org/jira/browse/AMBARI-17358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15351733#comment-15351733
]
Hadoop QA commented on AMBARI-17358:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12813792/AMBARI-17358.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 2 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/7565//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7565//console
This message is automatically generated.
> 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: trunk
>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)
