hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karthik Kambatla (JIRA)" <j...@apache.org>
Subject [jira] [Reopened] (HADOOP-12451) Setting HADOOP_HOME explicitly should be allowed
Date Tue, 06 Oct 2015 17:59:27 GMT

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

Karthik Kambatla reopened HADOOP-12451:

The committed patch avoids HADOOP_HOME is not overwritten.

In addition to this, HADOOP-11464 changes the behavior in yet another way. It actually sets
HADOOP_HOME whereas previously it was left empty. We realized we were relying on HADOOP_HOME
not being set at all, and it broke a bunch of things.

Should we change the patch to set HADOOP_HOME only if it is cygwin. Per [~aw]'s comment [here|https://issues.apache.org/jira/browse/HADOOP-12456?focusedCommentId=14940643&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14940643],
HADOOP_HOME is supported only on Windows.

> Setting HADOOP_HOME explicitly should be allowed
> ------------------------------------------------
>                 Key: HADOOP-12451
>                 URL: https://issues.apache.org/jira/browse/HADOOP-12451
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: scripts
>    Affects Versions: 2.7.1
>            Reporter: Karthik Kambatla
>            Assignee: Karthik Kambatla
>            Priority: Blocker
>             Fix For: 2.7.2
>         Attachments: HADOOP-12451-branch-2.1.patch
> HADOOP-11464 reinstates cygwin support. In the process, it sets HADOOP_HOME explicitly
in hadoop-config.sh without checking if it has already been set. 

This message was sent by Atlassian JIRA

View raw message