Mailing-List: contact hadoop-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hadoop-dev@lucene.apache.org
Message-ID: <20844247.1176240152798.JavaMail.jira@brutus>
Date: Tue, 10 Apr 2007 14:22:32 -0700 (PDT)
From: "Michael Bieniosek (JIRA)" <jira@apache.org>
To: hadoop-dev@lucene.apache.org
Subject: [jira] Commented: (HADOOP-1114) bin/hadoop script clobbers
 CLASSPATH
In-Reply-To: <18811152.1173745209233.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HADOOP-1114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12487926 ] 

Michael Bieniosek commented on HADOOP-1114:
-------------------------------------------

While I accept that using CLASSPATH for dependencies is fragile and hacky, I'm not sure why HADOOP_CLASSPATH is any different.  It seems both environment variables are equally abusable.  Using CLASSPATH is much more intuitive than the nonstandard HADOOP_CLASSPATH.  The only problem that HADOOP_CLASSPATH seems to solve is that a caller script might leave inherited garbage in CLASSPATH before adding more jars.  But that should be the responsibility of the caller script, I think.

> bin/hadoop script clobbers CLASSPATH
> ------------------------------------
>
>                 Key: HADOOP-1114
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1114
>             Project: Hadoop
>          Issue Type: Bug
>          Components: scripts
>    Affects Versions: 0.12.0
>            Reporter: Michael Bieniosek
>            Priority: Minor
>             Fix For: 0.13.0
>
>         Attachments: hadoop-no-clobber-classpath.patch
>
>
> The bin/hadoop script distributed with hadoop clobbers the user's CLASSPATH.  This prevents ad-hoc appending to the CLASSPATH.

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