>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 no alternative in the mapreduce
package is available.
On Mon, Jan 7, 2013 at 11:44 PM, Oleg Zhurakousky <
[EMAIL PROTECTED]> wrote:
> 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")