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.

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.

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

They were official, back around 2009, hence the first API was deprecated.

The reason that they removed the deprecation was that the 'new' API didn't have all of the features/methods of the old APIs.

I learned using the new APIs and ToolRunner is your friend.
So I would suggest using the new APIs.

But that's just me.
On Oct 24, 2012, at 5:02 AM, Alberto Cordioli <[EMAIL PROTECTED]> wrote:

> 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
>

Using either is fully supported in 2.x+ at least. Neither is
deprecated, but I'd personally recommend using the new API going
forward. There's no known major issues with it.

FWIW, Apache HBase uses the new API for its MR-side utilities.

But in any case - no worries if you stick with one over the other for
whatever reason, not until a couple more major releases I should think.

On Wed, Oct 24, 2012 at 5:16 PM, Michael Segel
<[EMAIL PROTECTED]> wrote:
> They were official, back around 2009, hence the first API was deprecated.
>
> The reason that they removed the deprecation was that the 'new' API didn't have all of the features/methods of the old APIs.
>
> I learned using the new APIs and ToolRunner is your friend.
> So I would suggest using the new APIs.
>
> But that's just me.
>
>
> On Oct 24, 2012, at 5:02 AM, Alberto Cordioli <[EMAIL PROTECTED]> wrote:
>
>> 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
>>
>

--
Harsh J

Thanks,
Alberto

On 24 October 2012 16:33, Harsh J <[EMAIL PROTECTED]> wrote:
> Using either is fully supported in 2.x+ at least. Neither is
> deprecated, but I'd personally recommend using the new API going
> forward. There's no known major issues with it.
>
> FWIW, Apache HBase uses the new API for its MR-side utilities.
>
> But in any case - no worries if you stick with one over the other for
> whatever reason, not until a couple more major releases I should think.
>
> On Wed, Oct 24, 2012 at 5:16 PM, Michael Segel
> <[EMAIL PROTECTED]> wrote:
>> They were official, back around 2009, hence the first API was deprecated.
>>
>> The reason that they removed the deprecation was that the 'new' API didn't have all of the features/methods of the old APIs.
>>
>> I learned using the new APIs and ToolRunner is your friend.
>> So I would suggest using the new APIs.
>>
>> But that's just me.
>>
>>
>> On Oct 24, 2012, at 5:02 AM, Alberto Cordioli <[EMAIL PROTECTED]> wrote:
>>
>>> 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
>>>
>>
>
>
>
> --
> Harsh J

--
Alberto Cordioli