I have no problem with your proposal, but have not tested it. If the unit
tests still run then go ahead and commit it. If this means we no longer need
They do run fine. No need to provide the JAR name (this has been included in the
patch).
D.
e.apache.org
> Subject: Re: Class Loader Problem
>
>
> Jeff, did you have a chance to try it? Can we close this issue?
>
> D.
>
> Dawid Weiss wrote:
> >
> > Hi Jeff,
> >
> > Like I said -- it seems that this issue is actually quite trivial to
>
f
-Original Message-
From: Dawid Weiss [mailto:[EMAIL PROTECTED] Sent:
Thursday, March 06, 2008 12:51 AM
To: mahout-dev@lucene.apache.org
Subject: Re: Class Loader Problem
Hi guys,
I just looked at the code and noticed you use Class-relative
classloader:
Class cl = Class.forName(job.ge
arch 06, 2008 12:51 AM
To: mahout-dev@lucene.apache.org
Subject: Re: Class Loader Problem
Hi guys,
I just looked at the code and noticed you use Class-relative
classloader:
Class cl = Class.forName(job.get(DISTANCE_MEASURE_KEY));
This is effectively an attempt to load a class using the calle
ROTECTED]
Sent: Thursday, March 06, 2008 12:51 AM
To: mahout-dev@lucene.apache.org
Subject: Re: Class Loader Problem
Hi guys,
I just looked at the code and noticed you use Class-relative
classloader:
Class cl = Class.forName(job.get(DISTANCE_MEASURE_KEY));
This is effectively an attempt to load a
> Jeff
>
> -Original Message-
> From: Dawid Weiss [mailto:[EMAIL PROTECTED]
> Sent: Thursday, March 06, 2008 12:51 AM
> To: mahout-dev@lucene.apache.org
> Subject: Re: Class Loader Problem
>
>
> Hi guys,
>
> I just looked at the code and noticed you u
classpath environment is different than that of a deployed map
task.
Jeff
-Original Message-
From: Dawid Weiss [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 06, 2008 12:51 AM
To: mahout-dev@lucene.apache.org
Subject: Re: Class Loader Problem
Hi guys,
I just looked at the code and notic
If you file a JIRA issue for this, Grant, I can test/ try different ways of
running the code without this explicit jar pointer.
Dawid
Grant Ingersoll wrote:
Yeah, I agree it is a headache for the future. It is already a bit
problematic in that we have to build the jar before tests are run.
Yeah, I agree it is a headache for the future. It is already a bit
problematic in that we have to build the jar before tests are run.
On Mar 6, 2008, at 5:30 AM, Dawid Weiss wrote:
As a side note -- Hadoop uses the simplest trick possible to figure
out the JAR location of the originating
As a side note -- Hadoop uses the simplest trick possible to figure out the JAR
location of the originating class -- it attempts to load a resource named after
the class' bytecode...
private static String findContainingJar(Class my_class) {
ClassLoader loader = my_class.getClassLoader()
I changed the main's to pass in the location of the jar, since the ANT
task puts the jar in basedir/dist. I made a comment about it on
Mahout-3. The Canopy driver should do the right thing? I also did
the same thing w/ the k-means.
I honestly don't think the JAR file must be specified
;apache-mahout-0.1-dev.jar");
DriverS.runJob(output + "/clusters", output);
} catch (IOException e) {
e.printStackTrace();
}
}
-Original Message-
From: Ted Dunning [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 05, 2008 11:44 AM
To: mahout-dev@lucene.apac
e) {
>> e.printStackTrace();
>>}
>> }
>>
>> -Original Message-
>> From: Ted Dunning [mailto:[EMAIL PROTECTED]
>> Sent: Wednesday, March 05, 2008 11:44 AM
>> To: mahout-dev@lucene.apache.org
>> Subject: Re: Class Loader Problem
>>
>>
>> Where is your code?
>>
>>
>> On 3/5/08 11:28 AM, "Jeff Eastman" <[EMAIL PROTECTED]> wrote:
>>
>>> I'm wondering if you can see anything
>>> wrong with my packaging or, perhaps, how the Canopy class is going
>> about
>>> instantiating it.
>>
>
>
Ingersoll [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 05, 2008 4:50 PM
To: mahout-dev@lucene.apache.org
Subject: Re: Class Loader Problem
I changed the main's to pass in the location of the jar, since the ANT
task puts the jar in basedir/dist. I made a comment about it on
Mahout-3.
(IOException e) {
e.printStackTrace();
}
}
-Original Message-
From: Ted Dunning [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 05, 2008 11:44 AM
To: mahout-dev@lucene.apache.org
Subject: Re: Class Loader Problem
Where is your code?
On 3/5/08 11:28 AM, "Jeff Eastman" <[EM
sting this happy result to the list so others can benefit from it in
the future.
Thanks Ted, (Grant),
Jeff
-Original Message-
From: Jeff Eastman [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 05, 2008 11:53 AM
To: mahout-dev@lucene.apache.org
Subject: RE: Class Loader Problem
Her
output);
} catch (IOException e) {
e.printStackTrace();
}
}
-Original Message-
From: Ted Dunning [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 05, 2008 11:44 AM
To: mahout-dev@lucene.apache.org
Subject: Re: Class Loader Problem
Where is your code?
On 3/5/08 11:28 AM, "Jeff Ea
Where is your code?
On 3/5/08 11:28 AM, "Jeff Eastman" <[EMAIL PROTECTED]> wrote:
> I'm wondering if you can see anything
> wrong with my packaging or, perhaps, how the Canopy class is going about
> instantiating it.
Ted, Grant,
I'm trying to use our canopy clustering code with my own distance
measure and I'm getting a class not found exception trying to load it.
My job, which ran great before I changed the distance measure, is
packaged in a jar file with the mahout-dev jar inside it in /lib. My job
calls t
19 matches
Mail list logo
