[ 
https://issues.apache.org/jira/browse/HADOOP-11393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15210442#comment-15210442
 ] 

Hadoop QA commented on HADOOP-11393:
------------------------------------

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m 0s 
{color} | {color:blue} Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red} 0m 9s {color} 
| {color:red} HADOOP-11393 does not apply to trunk. Rebase required? Wrong 
Branch? See https://wiki.apache.org/hadoop/HowToContribute for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Patch URL | 
https://issues.apache.org/jira/secure/attachment/12731641/HADOOP-11393.01.patch 
|
| JIRA Issue | HADOOP-11393 |
| Console output | 
https://builds.apache.org/job/PreCommit-HADOOP-Build/8914/console |
| Powered by | Apache Yetus 0.2.0   http://yetus.apache.org |


This message was automatically generated.



> Revert HADOOP_PREFIX, go back to HADOOP_HOME
> --------------------------------------------
>
>                 Key: HADOOP-11393
>                 URL: https://issues.apache.org/jira/browse/HADOOP-11393
>             Project: Hadoop Common
>          Issue Type: Improvement
>    Affects Versions: 3.0.0
>            Reporter: Allen Wittenauer
>            Assignee: Allen Wittenauer
>         Attachments: HADOOP-11393-00.patch, HADOOP-11393.01.patch
>
>
> Today, Windows and parts of the Hadoop source code still use HADOOP_HOME.  
> The switch to HADOOP_PREFIX back in 0.21 or so didn't really accomplish what 
> it was intended to do and only helped confuse the situation.
> _HOME is a much more standard suffix and is, in fact, used for everything in 
> Hadoop except for the top level project home.  I think it would be beneficial 
> to use HADOOP_HOME in the shell code as the Official(tm) variable, still 
> honoring HADOOP_PREFIX if it is set.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to