hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kay Kay <kaykay.uni...@gmail.com>
Subject Re: Vote on getting org.apache.hadoop.hbase.mapred back in 0.21
Date Fri, 15 Jan 2010 22:54:30 GMT
Not exactly a developer , but then +1 to maintain that since the 
stability of mapreduce-0.21 is a major source of concern (with the new 
packages) at this point with refactoring going on in that arena. It is 
going to be some time before that could be trusted entirely.

At that point in the future, may be we can also have   *.mapreduce.* 
packages going with the new classes as well.  Thanks.

On 1/15/10 2:02 PM, Jean-Daniel Cryans wrote:
> Hi devs,
> The removing of the old HBase mapred API while Hadoop 0.21 is still
> keeping it causes the situation where we are forcing users to migrate
> while they may not have to. Also, other projects like cascading
> continue to rely on the old Hadoop mapred API so their HBase module
> will break. This is very problematic.
> What I propose is that we get the org.apache.hadoop.hbase.mapred
> package back in 0.21. To do that, we need to refactor all the
> dependencies on the old client API to use the new one. The impact on
> users upgrading from 0.20 to 0.21 with MR jobs using the old package
> will be the same, they will have to change all the client calls in
> their code.
> This is ok with everyone?
> If the vote passes, I will do the work.
> J-D

View raw message