I know nothing of the history of that element on the HADOOP_CLASSPATH.  I
left it there assuming that someone, somewhere knew why it was there.

I know that with e.g. CDH4, that is not the correct location.

The Java system definitely ignores missing elements in this case.

Loren

On Fri, Feb 14, 2014 at 1:46 PM, P. Oscar Boykin
<notifications@github.com>wrote:

> In scripts/scald.rb:
>
> > @@ -464,8 +444,10 @@ def build_job_jar
> >  end
> >
> >  def hadoop_command
> > -  "HADOOP_CLASSPATH=/usr/share/java/hadoop-lzo-0.4.15.jar:#{JARBASE}:job-jars/#{JOBJAR} " +
> > -    "hadoop jar #{JARBASE} -libjars job-jars/#{JOBJAR} #{hadoop_opts} #{JOB} --hdfs " +
> > +  hadoop_classpath = (["/usr/share/java/hadoop-lzo-0.4.15.jar", JARBASE, MODULEJARPATHS.map{|n| File.basename(n)}, "job-jars/#{JOBJAR}"].select { |s| s != "" }).join(":")
>
> how does that hadoop-lzo get installed? Looks a bit suspect. Obviously, it
> was always there. I guess java ignores missing files?
>
> --
> Reply to this email directly or view it on GitHub<https://github.com/twitter/scalding/pull/788/files#r9761160>
> .
>