On Mon, May 9, 2011 at 8:36 AM, Benson Margulies <[email protected]>wrote: > > As a convenience (and a trap for the unwary), there is a convenience: > setJarByClass. This takes a Class<?> instead of a string jar path. It > attempts to derive a jar name from the class reference. >
Ok, this last bit is the piece of the puzzle I was missing / forgetting. > Mahout then has a series of self-contained classes that create JobConf > objects, and make calls to setJarByClass, passing Whatever.class. If > one of those classes somehow wanders into lib/ (like, a person > building a job jar puts mahout into 'lib/' and then tries to use a > Mahout job class) the call to setJarByClass is at best ineffective and > at worst destructive. > So that explains how some user rebundlings don't work with us, sometimes. What it doesn't explain is why running the regular, not-rebundled "mahout-examples-0.5-SNAPSHOT-job.jar" via the bin/mahout shell script is throwing this ClassNotFoundException for me (and it's happened to Sean, and according to the list archives, others as well) in a production cluster. -jake
