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] [Created] (AMBARI-13647) Changes to mapred-site configuration does not force Hive restart
Date Fri, 30 Oct 2015 02:41:27 GMT
Tuong Truong created AMBARI-13647:
-------------------------------------

             Summary: 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: 2.0.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