[
https://issues.apache.org/jira/browse/HADOOP-11393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14535071#comment-14535071
]
Allen Wittenauer commented on HADOOP-11393:
-------------------------------------------
Given that this would be trunk only, I think their is a high expectation that
people will be reviewing their shell code and call outs anyway given the amount
of change already present. Plus, now that we have deprecation code, we can
handle HADOOP_PREFIX so that a) it is still honored but with a warning and b)
so that we can actually remove it in hadoop 4.x (!) in a safe way.
> 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
> Labels: BB2015-05-TBR
> Attachments: HADOOP-11393-00.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)
