Return-Path: X-Original-To: apmail-ambari-dev-archive@www.apache.org Delivered-To: apmail-ambari-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 38479179B7 for ; Fri, 30 Oct 2015 02:41:34 +0000 (UTC) Received: (qmail 37137 invoked by uid 500); 30 Oct 2015 02:41:27 -0000 Delivered-To: apmail-ambari-dev-archive@ambari.apache.org Received: (qmail 37045 invoked by uid 500); 30 Oct 2015 02:41:27 -0000 Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ambari.apache.org Delivered-To: mailing list dev@ambari.apache.org Received: (qmail 36966 invoked by uid 99); 30 Oct 2015 02:41:27 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 30 Oct 2015 02:41:27 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id AFBA72C14E1 for ; Fri, 30 Oct 2015 02:41:27 +0000 (UTC) Date: Fri, 30 Oct 2015 02:41:27 +0000 (UTC) From: "Tuong Truong (JIRA)" To: dev@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (AMBARI-13647) Changes to mapred-site configuration does not force Hive restart MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 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)