The idea would be to move off of JobClient too, I believe. The running theory is that we're trying to standardize on one approach, and about half the code is using this thing inside Mahout called AbstractJob that is the current way we're standardizing. It uses the 0.20.x APIs.
Updating anything to use that would be great, though it's a bit more work. Just emulating the way it invokes jobs would be a step forward if it moved off of the 0.19.x APIs. You are right that some things that were deprecated are becoming un-deprecated. My impression is that we're still "supposed" to be migrating to 0.20.x APIs, even when using 0.21 and beyond. (We can't use 0.21 just now, yes, in any event.) I suggest it's still a worthy task since at the moment it's still suboptimal to have different ways to run jobs. On Thu, Jan 6, 2011 at 4:55 AM, Walter Gillett <[email protected]> wrote: > I looked into removing the use of JobConf, but looks like it's too early to do > that. Removing JobConf from Mahout would require removing JobClient as well. > In > this email thread I see: >
