Thanks Bejoy, my only concern is that the new api were to become "official" quite some time ago, but this seems to be a long process. And honestly I don't understand why. The changes are not so invasive. I just want to be sure to learn the more suitable api for the future.
Anyway, as you said, let's see if a committer can comment on this. Alberto On 22 October 2012 15:40, Bejoy KS <[email protected]> wrote: > Hi alberto > > The new mapreduce API is coming to shape now. The majority of the classes > available in old API has been ported to new API as well. > > The Old mapred API was marked depreciated in an earlier version of hadoop > (0.20.x) but later it was un-depreciated as all the functionality in old API > was not available in new mapreduce API at that point. > > Now mapreduce API is pretty good and you can go ahead with that for > development. AFAIK mapreduce API is the future. > > Let's wait for a commiter to officially comment on this. > > Regards > Bejoy KS > > Sent from handheld, please excuse typos. > > -----Original Message----- > From: Alberto Cordioli <[email protected]> > Date: Mon, 22 Oct 2012 15:22:41 > To: <[email protected]> > Reply-To: [email protected] > Subject: Old vs New API > > Hi all, > > I am using last stable Hadoop version (1.0.3) and I am implementing > right now my first MR jobs. > I read about the presence of 2 API: the old and the new one. I read > some stuff about them, but I am not able to find quite fresh news. > I read that the old api was deprecated, but in my version they do not > seem to. Moreover the new api does not have all the features > implemented (see for example the package contrib with its classes to > do joins). > > I found this post on the ML: > <http://mail-archives.apache.org/mod_mbox/hadoop-common-user/201002.mbox/%[email protected]%3E> > but it is very old (2010) and I think that further changes have been > made meanwhile. > > My question is: does make sense to use the new api, instead of the old > one? Does this new version providing other functionalities with > respect to the older one? > Or, given the slow progress in implementation, is better to use the old api? > > > Thanks. -- Alberto Cordioli
