ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tuong Truong (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-13647) Changes to mapred-site configuration does not force Hive restart
Date Fri, 30 Oct 2015 21:42:27 GMT

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

Tuong Truong commented on AMBARI-13647:
---------------------------------------

Looks like this was fixed in 2.1.2+ in August by JIRA AMBARI-12894 Changing mapreduce.application.classpath
via Ambari doesn't prompt for Hive Restart (dsen)

> Changes to mapred-site configuration does not force Hive restart
> ----------------------------------------------------------------
>
>                 Key: AMBARI-13647
>                 URL: https://issues.apache.org/jira/browse/AMBARI-13647
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 1.7.0
>            Reporter: Tuong Truong
>
> Hive conf directory has a copy of mapred-site.xml that is generated when Hive is restarted.
 This copy is used by Hive to run MR jobs.  When mapred-site configuration is change, Hive
service is not flagged for restart since only after restarting of Hive that the mapred-site.xml
in /etc/hive/conf is regenerated.  
> As a result, mapred-site configuration changes does not take effect for Hive until Hive
is restarted.
> The change that caused this issue was a deliberate change in  JIRA-6482



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

Mime
View raw message