More to the point of your actual question, it looks to me like
o.a.m.df.mapreduce.* does superscede o.a.m.df.mapred.* as it employs the
new APIs as below.
On 6/14/10 11:22 AM, Jeff Eastman wrote:
If you mean o.a.h.mapreduce.* then yes, mostly that. I found the
drivers needed their JobConf stuff divided among Configuration and Job
classes and the Mappers and Reducers needed new setup and cleanup
methods with changes also due to the JobConf->Configuration/Job
splits. Then the unit tests needed tweaking, particularly the Mapper
and Reducer tests which needed MockMapperContexts and
MockReducerContexts. Some of the driver stuff can be simplified by
using the AbstractJob superclass methods and I will do that next in
clustering.
Have fun,
Jeff
On 6/14/10 10:43 AM, Sean Owen wrote:
I'm about to make one of those big patches again. This time to push to
update to use the new Hadoop APIs everywhere (purely updating the API
calls).
Am I right that o.a.m.df.mapreduce.* duplicates and supersedes
o.a.m.df.mapred.*, the difference being that the former uses new APIs
already? I have this from an earlier message but want to confirm.
Sean
