You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by hongbin ma <ma...@apache.org> on 2015/03/25 04:37:31 UTC
TableInputFormatBase deprecated issue
hi, all
I found this class TableInputFormatBase deprecated in 0.98, but
un-deprecated in https://issues.apache.org/jira/browse/HBASE-11178.
I'm wondering why is the change?
Does it mean we nearly discarded its support to mapred over hbase?
I'm thinking about using hbase as my MR's input and sink,
please let me know if it's feasible to do it.
--
Regards,
*Bin Mahone | 马洪宾*
Apache Kylin: http://kylin.io
Github: https://github.com/binmahone
Re: TableInputFormatBase deprecated issue
Posted by hongbin ma <ma...@apache.org>.
thanks Elliott,
it' very clear explanation
On Wed, Mar 25, 2015 at 12:35 PM, Elliott Clark <ec...@apache.org> wrote:
> All of the code in mapred was considered deprecated because Hadoop had been
> saying for a while that org.apache.hadoo.mapreduce (as opposed to
> org.apache.hadoop.mapred) would be best supported MR framework. So HBase
> wanted to push users to use that set of classes.
>
> However it's become pretty apparent that way too many applications have
> been built on both of the different sets of classes. Hence Hadoop will have
> to support mapred and mapreduce fully. Hence HBase will support both, as we
> want users to have the best options available.
>
> If it were me creating new code I would still choose
>
> https://github.com/apache/hbase/blob/master/hbase-server/src/main/java/org/apache/hadoop/hbase/mapreduce/TableInputFormat.java
> over
>
> https://github.com/apache/hbase/blob/master/hbase-server/src/main/java/org/apache/hadoop/hbase/mapred/TableInputFormat.java
>
>
> On Tue, Mar 24, 2015 at 8:37 PM, hongbin ma <ma...@apache.org> wrote:
>
> > hi, all
> >
> > I found this class TableInputFormatBase deprecated in 0.98, but
> > un-deprecated in https://issues.apache.org/jira/browse/HBASE-11178.
> >
> > I'm wondering why is the change?
> > Does it mean we nearly discarded its support to mapred over hbase?
> >
> > I'm thinking about using hbase as my MR's input and sink,
> > please let me know if it's feasible to do it.
> >
> > --
> > Regards,
> >
> > *Bin Mahone | 马洪宾*
> > Apache Kylin: http://kylin.io
> > Github: https://github.com/binmahone
> >
>
--
Regards,
*Bin Mahone | 马洪宾*
Apache Kylin: http://kylin.io
Github: https://github.com/binmahone
Re: TableInputFormatBase deprecated issue
Posted by Elliott Clark <ec...@apache.org>.
All of the code in mapred was considered deprecated because Hadoop had been
saying for a while that org.apache.hadoo.mapreduce (as opposed to
org.apache.hadoop.mapred) would be best supported MR framework. So HBase
wanted to push users to use that set of classes.
However it's become pretty apparent that way too many applications have
been built on both of the different sets of classes. Hence Hadoop will have
to support mapred and mapreduce fully. Hence HBase will support both, as we
want users to have the best options available.
If it were me creating new code I would still choose
https://github.com/apache/hbase/blob/master/hbase-server/src/main/java/org/apache/hadoop/hbase/mapreduce/TableInputFormat.java
over
https://github.com/apache/hbase/blob/master/hbase-server/src/main/java/org/apache/hadoop/hbase/mapred/TableInputFormat.java
On Tue, Mar 24, 2015 at 8:37 PM, hongbin ma <ma...@apache.org> wrote:
> hi, all
>
> I found this class TableInputFormatBase deprecated in 0.98, but
> un-deprecated in https://issues.apache.org/jira/browse/HBASE-11178.
>
> I'm wondering why is the change?
> Does it mean we nearly discarded its support to mapred over hbase?
>
> I'm thinking about using hbase as my MR's input and sink,
> please let me know if it's feasible to do it.
>
> --
> Regards,
>
> *Bin Mahone | 马洪宾*
> Apache Kylin: http://kylin.io
> Github: https://github.com/binmahone
>