Hmmm...
Is there a more elegant way to go here? Is there a way for the
CanopyClusteringJob to infer which jar by looking at the class? I think
that Hadoop does something like this via the class loader.
This current method looks ripe for very obscure bugs.
On 3/5/08 4:49 PM, "Grant Ingersoll" <[EMAIL PROTECTED]> wrote:
> 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.
>
>
> On Mar 5, 2008, at 2:52 PM, Jeff Eastman wrote:
>
>> Here's my job driver, it works fine with ManhattanDistanceMeasure but
>> not SystemLoadDistanceMeasure.
>>
>> Jeff
>>
>> public static void main(String[] args) {
>> String input = args[0];
>> String output = args[1];
>> int t1 = new Integer(args[2]);
>> int t2 = new Integer(args[3]);
>> JobConf conf = new JobConf(
>> com.collabnet.hadoop.systemload.access.DriverA.class);
>> Path outPath = new Path(output);
>> try {
>> FileSystem dfs = FileSystem.get(conf);
>> if (dfs.exists(outPath))
>> dfs.delete(outPath);
>> DriverA.runJob(input, output);
>> DriverP.runJob(input, output);
>> DriverC.runJob(output, output);
>> CanopyClusteringJob.runJob(output + "/combined", output,
>> SystemLoadDistanceMeasure.class.getName(), t1, t2,
>> "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: [email protected]
>> 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.
>>
>
>
