You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Eli Collins (JIRA)" <ji...@apache.org> on 2010/09/12 00:05:33 UTC
[jira] Commented: (HADOOP-6950) Suggest that HADOOP_CLASSPATH
should be preserved in hadoop-env.sh.template
[ https://issues.apache.org/jira/browse/HADOOP-6950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12908375#action_12908375 ]
Eli Collins commented on HADOOP-6950:
-------------------------------------
+1 Seems reasonable. Thanks Philip.
> 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
> 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.