You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-user@hadoop.apache.org by Sanjeev Verma <sa...@gmail.com> on 2011/12/24 02:23:57 UTC

Question on deprecations in Hadoop 0.20.203.0 API

Hey everyone:

I am going through the "hadoop in action" book, and I guess the version of
hadoop that book refers to is already old :-). The installation I have is
0.20.203.0, and in this version, a few key base classes have been
deprecated, like:

Interface InputSplit is deprecated in favor of InputSplit abstract class

class org.apache.hadoop.mapred.LineRecordReader is deprecated in favor of
org.apache.hadoop.mapreduce.lib.input.LineRecordReader

Without knowing in detail why these deprecation decisions were made, it
seems a bit adhoc to me (I am definitely missing something, I am sure...).
For example, while the deprecated LineRecordReader does have a replacement
in the org.apache.hadoop.mapreduce.lib.input package, I see that another
reader, KeyValueLineRecordReader, has not bee deprecated while it is
internally using the deprecated LineRecordReader. So i guess my question
is, why?

Thanks in advance

Regards
Sanjeev

Re: Question on deprecations in Hadoop 0.20.203.0 API

Posted by Sanjeev Verma <sa...@gmail.com>.

Thanks Harsh!
On Dec 23, 2011 11:21 PM, "Harsh J" <ha...@cloudera.com> wrote:

> These items have been un-deprecated in 0.20.205+, and is also supported in
> 0.22/0.23+. The deprecated APIs are now the stable ones again, and you
> shouldn't carry further confusion while using it.
>
> On 24-Dec-2011, at 6:53 AM, Sanjeev Verma wrote:
>
> > Hey everyone:
> >
> > I am going through the "hadoop in action" book, and I guess the version
> of
> > hadoop that book refers to is already old :-). The installation I have is
> > 0.20.203.0, and in this version, a few key base classes have been
> > deprecated, like:
> >
> > Interface InputSplit is deprecated in favor of InputSplit abstract class
> >
> > class org.apache.hadoop.mapred.LineRecordReader is deprecated in favor of
> > org.apache.hadoop.mapreduce.lib.input.LineRecordReader
> >
> > Without knowing in detail why these deprecation decisions were made, it
> > seems a bit adhoc to me (I am definitely missing something, I am
> sure...).
> > For example, while the deprecated LineRecordReader does have a
> replacement
> > in the org.apache.hadoop.mapreduce.lib.input package, I see that another
> > reader, KeyValueLineRecordReader, has not bee deprecated while it is
> > internally using the deprecated LineRecordReader. So i guess my question
> > is, why?
> >
> > Thanks in advance
> >
> > Regards
> > Sanjeev
>
>

Re: Question on deprecations in Hadoop 0.20.203.0 API

Posted by Harsh J <ha...@cloudera.com>.

These items have been un-deprecated in 0.20.205+, and is also supported in 0.22/0.23+. The deprecated APIs are now the stable ones again, and you shouldn't carry further confusion while using it.

On 24-Dec-2011, at 6:53 AM, Sanjeev Verma wrote:

> Hey everyone:
> 
> I am going through the "hadoop in action" book, and I guess the version of
> hadoop that book refers to is already old :-). The installation I have is
> 0.20.203.0, and in this version, a few key base classes have been
> deprecated, like:
> 
> Interface InputSplit is deprecated in favor of InputSplit abstract class
> 
> class org.apache.hadoop.mapred.LineRecordReader is deprecated in favor of
> org.apache.hadoop.mapreduce.lib.input.LineRecordReader
> 
> Without knowing in detail why these deprecation decisions were made, it
> seems a bit adhoc to me (I am definitely missing something, I am sure...).
> For example, while the deprecated LineRecordReader does have a replacement
> in the org.apache.hadoop.mapreduce.lib.input package, I see that another
> reader, KeyValueLineRecordReader, has not bee deprecated while it is
> internally using the deprecated LineRecordReader. So i guess my question
> is, why?
> 
> Thanks in advance
> 
> Regards
> Sanjeev