hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eli Collins (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (HADOOP-6950) Suggest that HADOOP_CLASSPATH should be preserved in hadoop-env.sh.template
Date Thu, 16 Sep 2010 02:35:34 GMT

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

Eli Collins resolved HADOOP-6950.
---------------------------------

    Resolution: Fixed

> 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: Improvement
>          Components: scripts
>    Affects Versions: 0.22.0
>            Reporter: Philip Zeyliger
>            Assignee: Philip Zeyliger
>            Priority: Trivial
>             Fix For: 0.22.0
>
>         Attachments: HADOOP-6950.patch.txt
>
>
> 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.


Mime
View raw message