+1 since Hadoop 0.21 is keeping it.
----- Original Message ----
> From: Jean-Daniel Cryans <jdcry...@apache.org>
> To: HBase Dev List <hbase-dev@hadoop.apache.org>
> Sent: Fri, January 15, 2010 2:02:26 PM
> Subject: Vote on getting org.apache.hadoop.hbase.mapred back in 0.21
>
> 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
