Hi Tom,
that's exactly it. Thanks! I don't think that I can comment on the
issues in Jira so I will do it here.
Tricking with class paths and deviating from the default class loading
delegation has never been anything but a short term relieve. Fixing
things by imposing a better order of
1. Classloader business can be done right. Actually it could be done as
spec-ed for servlet web-apps.
2. If the issue is strictly 'too large classpath', then a simpler solution
would be to sof-link all JARs to the current directory and create the
classpath with the JAR names only (no path). Note
Hello,
I'm getting a ClassCastException, when running my application:
10/10/07 04:31:10 WARN mapred.LocalJobRunner: job_local_0001
java.lang.ClassCastException: class java.util.Date
at java.lang.Class.asSubclass(Class.java:3018)
at
Hello,
How do I run my Hadoop application within Eclipse? I've compiled the
plugin, but the following exception occurs (if run as run on hadoop or
java application).
10/10/07 05:03:11 WARN conf.Configuration: DEPRECATED: hadoop-site.xml
found in the classpath. Usage of hadoop-site.xml is
Hadoop is attempting to cast a Date object to WritableComparable, which
Date does not implement, and is causing that exception.
Your keys must implement WritableComparable and your values must
implement Comparable.
On Wed, Oct 6, 2010 at 8:02 PM, Johannes.Lichtenberger
[sent too soon]
The first CP shown is how it is today the CP of a task. If we change it pick
up all the job JARs from the current dir, then the classpath will be much
shorter (second CP shown). We can easily achieve this by soft-linking the
job JARs in the work dir of the task.
Alejandro
On
