Interesting and strange. but are there any reason for setting $HADOOP_HOME to $HADOOP_PREFIX in hadoop-conf.sh and then checking in /bin/hadoop.sh whether $HADOOP_HOME is not equal to ""
I mean if I comment out the export HADOOP_HOME=${HADOOP_PREFIX} in hadoop-conf.sh, does it make any difference ? Thanks, Praveenesh On Wed, Feb 1, 2012 at 6:04 PM, Prashant Sharma <prashan...@imaginea.com>wrote: > I think you have misunderstood something. AFAIK or understand these > variables are set automatically when you run a script. it's name is obscure > for some strange reason. ;). > > Warning: $HADOOP_HOME is deprecated is always there. whether the variable > is set or not. Why? > Because the hadoop-config is sourced in all scripts. And all it does is > sets HADOOP_PREFIX as HADOOP_HOME. I think this can be reported as a bug. > > -P > > > On Wed, Feb 1, 2012 at 5:46 PM, praveenesh kumar <praveen...@gmail.com > >wrote: > > > Does anyone have idea on Why $HADOOP_PREFIX was introduced instead of > > $HADOOP_HOME in hadoop 0.20.205 ? > > > > I believe $HADOOP_HOME was not giving any troubles or is there a > reason/new > > feature that require $HADOOP_PREFIX to be added ? > > > > Its a kind of funny, but I got habitual of using $HADOOP_HOME. Just > curious > > to know for this change. > > Also, there are some old packages ( I am not referring apache/cloudera/or > > any hadoop distribution ), that depends on hadoop that still uses > > $HADOOP_HOME inside. So its kind of weird when you use those packages, > you > > still get warning messages even though its suppressed from Hadoop side. > > > > > > Thanks, > > Praveenesh > > >