Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Sat, 12 Sep 2015 01:01:46 +0000 (UTC)
From: "Vijay Srinivasaraghavan (JIRA)" <jira@apache.org>
To: dev@ambari.apache.org
Message-ID: <JIRA.12857855.1440164765000.320593.1442019706859@Atlassian.JIRA>
In-Reply-To: <JIRA.12857855.1440164765000@Atlassian.JIRA>
References: <JIRA.12857855.1440164765000@Atlassian.JIRA>
 <JIRA.12857855.1440164765735@arcas>
Subject: [jira] [Resolved] (AMBARI-12851) The definition and hadling of
 hadoop-env should not be restrictive to HDFS
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Vijay Srinivasaraghavan resolved AMBARI-12851.
----------------------------------------------
       Resolution: Fixed
    Fix Version/s: trunk

Addressed in AMBARI-12837

> The definition and hadling of hadoop-env should not be restrictive to HDFS
> --------------------------------------------------------------------------
>
>                 Key: AMBARI-12851
>                 URL: https://issues.apache.org/jira/browse/AMBARI-12851
>             Project: Ambari
>          Issue Type: Bug
>            Reporter: Vijay Srinivasaraghavan
>            Assignee: Sumit Mohanty
>             Fix For: trunk
>
>
> Hadoop Env configuration defined at the stack level is managed only if HDFS  service is slected as part of the deployment. If HDFS is disabled and any alternate FS includes hadoop-env in the stack, the configuration should be understood by the Ambari code and corresponding hadoop-env.sh should be created properly on the hadoop/ambari agent machines.


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