Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Message-ID: <23469743.124841284146199743.JavaMail.jira@thor>
Date: Fri, 10 Sep 2010 15:16:39 -0400 (EDT)
From: "Philip Zeyliger (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Subject: [jira] Created: (HADOOP-6950) Suggest that HADOOP_CLASSPATH should
 be preserved in hadoop-env.sh.template
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Suggest that HADOOP_CLASSPATH should be preserved in hadoop-env.sh.template
---------------------------------------------------------------------------

                 Key: HADOOP-6950
                 URL: https://issues.apache.org/jira/browse/HADOOP-6950
             Project: Hadoop Common
          Issue Type: Bug
          Components: scripts
            Reporter: Philip Zeyliger
            Priority: Trivial


HADOOP_CLASSPATH tends to be used to add to bin/hadoop's classpath.  Because of the way the comment is written, administrator's who customize hadoop-env.sh often inadvertently disable user's abilities to use it, by not including the present value of the variable.

I propose we change the commented out suggestion code to include the present value.

{noformat}
 # Extra Java CLASSPATH elements.  Optional.
-# export HADOOP_CLASSPATH=
+# export HADOOP_CLASSPATH="<extra_entries>:$HADOOP_CLASSPATH"
{noformat}

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.