ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nate Cole (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-8156) Usability: Do not force a mysql restart to apply Hive changes
Date Fri, 07 Nov 2014 18:15:33 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-8156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14202372#comment-14202372
] 

Nate Cole commented on AMBARI-8156:
-----------------------------------

commit af31f3ec343043bb39e54175e7deb3f6950fa481

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

Mime
View raw message