Re: o.a.h.mapred package dependency: haven't we been over this a thousand times?
If we are not *forcing* our users to upgrade Hadoop past 0.20.2-ish, and we want to have nice things like mapside joins, ChainMapper/ChainReducer, and MultipleOutputs, then we're sometimes stuck in the old-and-faded API of yesteryear (org.apache.hadoop.mapred). Am I forgetting some trick which allows us to get around this, or some decision we made which makes this not relevant? -jake On Jan 13, 2012 11:36 AM, "Sean Owen" <sro...@gmail.com> wrote: I would not want to make moves that require people to be on a version later than 0.20.2 at this point. "Most" users have access to 0.20.2 or a work-alike (roughly, CDH3, Amazon EMR); few have access to 1.0 or 0.22+. Mahout should probably be a little behind the cutting edge in this regard. (That said I don't know of a reason it wouldn't all work with 1.0, unless it's some really tiny detail or API change.) I think branching is unnecessarily complex right now just for the sake of one dependency, albeit a major one. If anyone's itching to do some work here -- please look at replacing the deprecated .mapred. code. This has been sitting for nearly 2 years and so anything that nobody including the original author cares to update, I'd honestly say we consider dropping soon, having put it out in 0.6. On Fri, Jan 13, 2012 at 7:31 PM, Dmitriy Lyubimov <dlie...@gmail.com> wrote: > Alternatively, we ca...
