[jira] [Commented] (AMBARI-12894) Changing mapreduce.application.classpath via Ambari doesn't prompt for Hive Restart

["Hudson (JIRA)" <ji...@apache.org>]

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

Hudson commented on AMBARI-12894:
---------------------------------

SUCCESS: Integrated in Ambari-trunk-Commit #3333 (See [https://builds.apache.org/job/Ambari-trunk-Commit/3333/])
AMBARI-12894 Changing mapreduce.application.classpath via Ambari doesn't prompt for Hive Restart (dsen) (dsen: http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=34b4f9e267b9502c69ce84c0deca279a2b624bc4)
* ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/metainfo.xml


> Changing mapreduce.application.classpath via Ambari doesn't prompt for Hive Restart
> -----------------------------------------------------------------------------------
>
>                 Key: AMBARI-12894
>                 URL: https://issues.apache.org/jira/browse/AMBARI-12894
>             Project: Ambari
>          Issue Type: Bug
>          Components: stacks
>    Affects Versions: 2.0.1
>            Reporter: Dmytro Sen
>            Assignee: Dmytro Sen
>            Priority: Critical
>             Fix For: 2.1.2
>
>         Attachments: AMBARI-12894.patch
>
>
> When you change mapreduce.application.classpath under Ambari, it requests that you restart MapReduce and Yarn. At that time, you have a stale mapred-site.xml under /etc/hive/conf. Current workaround is to restart the Hive service.
> I have verified this by simply changing the mapreduce.application.classpath parameter under Ambari and noticed that hive is not labeled for restart.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)