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

Posted to dev@hbase.apache.org by William Temperley <wi...@gmail.com> on 2015/01/26 15:07:16 UTC

TableMapReduceUtil.initTableMapperJob

Dear all,

Issue HBASE-7024 <https://issues.apache.org/jira/browse/HBASE-7024> has
been closed and the restrictions on types of outputKeyClass and
outputValueClass were removed for most overloads of
TableMapReduceUtil.initTableMapperJob. These restrictions however remain
for the  three overloads which take List<Scan>.   I'm not sure if these
overloads were added later, or just missed in the previous patch.

I can't seem to reopen this issue, perhaps because I don't have permissions
as I only just signed up on JIRA.  Anyway I attached a patch to the issue,
which removes these type restrictions on the three methods taking multiple
scans.

Best regards,

Will Temperley

Re: TableMapReduceUtil.initTableMapperJob

Posted by Ted Yu <yu...@gmail.com>.

Please open a new JIRA and attach your patch there.

Cheers

On Mon, Jan 26, 2015 at 6:07 AM, William Temperley <wi...@gmail.com>
wrote:

> Dear all,
>
> Issue HBASE-7024 <https://issues.apache.org/jira/browse/HBASE-7024> has
> been closed and the restrictions on types of outputKeyClass and
> outputValueClass were removed for most overloads of
> TableMapReduceUtil.initTableMapperJob. These restrictions however remain
> for the  three overloads which take List<Scan>.   I'm not sure if these
> overloads were added later, or just missed in the previous patch.
>
> I can't seem to reopen this issue, perhaps because I don't have permissions
> as I only just signed up on JIRA.  Anyway I attached a patch to the issue,
> which removes these type restrictions on the three methods taking multiple
> scans.
>
> Best regards,
>
> Will Temperley
>