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 "Philip Zeyliger (JIRA)" <ji...@apache.org> on 2010/09/10 21:16:39 UTC
[jira] Created: (HADOOP-6950) Suggest that HADOOP_CLASSPATH should
be preserved in hadoop-env.sh.template
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.
[jira] Commented: (HADOOP-6950) Suggest that HADOOP_CLASSPATH
should be preserved in hadoop-env.sh.template
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-6950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12910097#action_12910097 ]
Hudson commented on HADOOP-6950:
--------------------------------
Integrated in Hadoop-Common-trunk #452 (See [https://hudson.apache.org/hudson/job/Hadoop-Common-trunk/452/])
HADOOP-6950. Suggest that HADOOP_CLASSPATH should be preserved in hadoop-env.sh.template. Contributed by Philip Zeyliger.
> 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.
[jira] Updated: (HADOOP-6950) Suggest that HADOOP_CLASSPATH should
be preserved in hadoop-env.sh.template
Posted by "Eli Collins (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-6950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eli Collins updated HADOOP-6950:
--------------------------------
Issue Type: Improvement (was: Bug)
I've committed this. 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: 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.
[jira] Updated: (HADOOP-6950) Suggest that HADOOP_CLASSPATH should
be preserved in hadoop-env.sh.template
Posted by "Philip Zeyliger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-6950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Philip Zeyliger updated HADOOP-6950:
------------------------------------
Attachment: HADOOP-6950.patch.txt
Patch attached. This is a comment/doc change.
> 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.
[jira] Commented: (HADOOP-6950) Suggest that HADOOP_CLASSPATH
should be preserved in hadoop-env.sh.template
Posted by "Eli Collins (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Resolved: (HADOOP-6950) Suggest that HADOOP_CLASSPATH should
be preserved in hadoop-env.sh.template
Posted by "Eli Collins (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (HADOOP-6950) Suggest that HADOOP_CLASSPATH
should be preserved in hadoop-env.sh.template
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-6950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12909997#action_12909997 ]
Hudson commented on HADOOP-6950:
--------------------------------
Integrated in Hadoop-Common-trunk-Commit #376 (See [https://hudson.apache.org/hudson/job/Hadoop-Common-trunk-Commit/376/])
HADOOP-6950. Suggest that HADOOP_CLASSPATH should be preserved in hadoop-env.sh.template. Contributed by Philip Zeyliger.
> 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.
[jira] Updated: (HADOOP-6950) Suggest that HADOOP_CLASSPATH should
be preserved in hadoop-env.sh.template
Posted by "Eli Collins (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-6950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eli Collins updated HADOOP-6950:
--------------------------------
Hadoop Flags: [Reviewed]
Assignee: Philip Zeyliger
Fix Version/s: 0.22.0
Affects Version/s: 0.22.0
> 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
> 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.