Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-dev@hadoop.apache.org
Message-ID: <2116560634.1240263647553.JavaMail.jira@brutus>
Date: Mon, 20 Apr 2009 14:40:47 -0700 (PDT)
From: "Doug Cutting (JIRA)" <jira@apache.org>
To: core-dev@hadoop.apache.org
Subject: [jira] Commented: (HADOOP-5702) hadoop-config.sh blows away
 CLASSPATH env
In-Reply-To: <2029726229.1240005734900.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-5702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12700953#action_12700953 ] 

Doug Cutting commented on HADOOP-5702:
--------------------------------------

> I think it's more intuitive for users to be able to use the normal CLASSPATH env var.

It's also more error prone.  For example, I've seen application installers that set CLASSPATH globally.

> hadoop-config.sh blows away CLASSPATH env
> -----------------------------------------
>
>                 Key: HADOOP-5702
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5702
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: scripts
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>         Attachments: HADOOP-5702.txt
>
>
> The bin/hadoop-config.sh script blows away the user's CLASSPATH environment variable when setting up the hadoop-specific classpath. It's possible that this is intentional, but it would make developing contrib service plugins (eg HADOOP-4707) easier if hadoop-config appended rather than replaced CLASSPATH.
> Attaching trivial patch to change this behavior.

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