Differences between 'mapped' and 'mapreduce' packages

2013-01-07 Thread Oleg Zhurakousky
What is the differences between the two? It seems like MR job could be configured using one of the other (e.g, extends MapReduceBase implements Mapper of extends Mapper) Cheers Oleg

Re: Differences between 'mapped' and 'mapreduce' packages

2013-01-07 Thread Sandeep Dukkipati
I am a little new to the hadoop world. But based on my readings and understanding thus far, there is not much functionality difference. Only difference is new API allows you to implement push and pull mechanisms in your map/reduce tasks as against push in old API. Mapper has been changed to super

Re: Differences between 'mapped' and 'mapreduce' packages

2013-01-07 Thread Mahesh Balija
Hi Oleg, Mapreduce 0.20.* api has the support for both 0.19 api (which is MapRed package in which your mapper should extend MRBase and implements Mapper) and it has the new api as well (which is MapReduce packages where you directly extend Mapper). As there are significant

Re: Differences between 'mapped' and 'mapreduce' packages

2013-01-07 Thread Hemanth Yamijala
From a user perspective, at a high level, the mapreduce package can be thought of as having user facing client code that can be invoked, extended etc as applicable from client programs. The mapred package is to be treated as internal to the mapreduce system, and shouldn't directly be used unless