[
https://issues.apache.org/jira/browse/AMBARI-8156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14201831#comment-14201831
]
Hadoop QA commented on AMBARI-8156:
-----------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12680113/AMBARI-8156.patch.2
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 1 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-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/542//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/542//console
This message is automatically generated.
> Usability: Do not force a mysql restart to apply Hive changes
> -------------------------------------------------------------
>
> Key: AMBARI-8156
> URL: https://issues.apache.org/jira/browse/AMBARI-8156
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-server
> Affects Versions: 1.7.0
> Reporter: Szilard Nemethy
> Assignee: Szilard Nemethy
> Labels: ambari-server
> Fix For: 2.0.0
>
> Attachments: AMBARI-8156.patch.2
>
>
> Ambari currently requires all services under tab to be restarted when changes
> are made to the configuration. This includes forcing a mysql restart when
> Hive settings are changed. Mysql should only have to be restarted when
> settings specific to mysql get changed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
