You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ambari.apache.org by "Dmytro Sen (JIRA)" <ji...@apache.org> on 2015/08/27 11:18:46 UTC

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

     [ https://issues.apache.org/jira/browse/AMBARI-12894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dmytro Sen updated AMBARI-12894:
--------------------------------
    Attachment: AMBARI-12894.patch

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