[
https://issues.apache.org/jira/browse/AMBARI-8156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14202485#comment-14202485
]
Hudson commented on AMBARI-8156:
--------------------------------
SUCCESS: Integrated in Ambari-trunk-Commit-docker #157 (See
[https://builds.apache.org/job/Ambari-trunk-Commit-docker/157/])
AMBARI-8156. Usability: Do not force a mysql restart to apply Hive changes (via
ncole) (ncole:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=af31f3ec343043bb39e54175e7deb3f6950fa481)
* ambari-server/src/test/resources/stacks/HDP/2.0.5/services/HIVE/metainfo.xml
* ambari-server/src/main/resources/stacks/HDP/2.1/services/HIVE/metainfo.xml
* ambari-server/src/main/resources/stacks/HDP/2.0.6/services/HIVE/metainfo.xml
> 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)
