[
https://issues.apache.org/jira/browse/HBASE-12929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14300841#comment-14300841
]
Hudson commented on HBASE-12929:
--------------------------------
SUCCESS: Integrated in HBase-1.0 #705 (See
[https://builds.apache.org/job/HBase-1.0/705/])
HBASE-12929 TableMapReduceUtil.initTableMapperJob unnecessarily limits the
types of outputKeyClass and outputValueClass (Will Temperley) (enis: rev
c1b587ea9b8a1ea9a7aa588bd641f3fa0974e73d)
*
hbase-server/src/main/java/org/apache/hadoop/hbase/mapreduce/TableMapReduceUtil.java
> TableMapReduceUtil.initTableMapperJob unnecessarily limits the types of
> outputKeyClass and outputValueClass
> -----------------------------------------------------------------------------------------------------------
>
> Key: HBASE-12929
> URL: https://issues.apache.org/jira/browse/HBASE-12929
> Project: HBase
> Issue Type: Improvement
> Components: mapreduce
> Reporter: Will Temperley
> Priority: Minor
> Labels: mapreduce
> Fix For: 1.0.0, 2.0.0, 1.1.0
>
> Attachments: HBASE-12929.patch
>
> Original Estimate: 2h
> Remaining Estimate: 2h
>
> The initTableMapperJob methods in TableMapReduceUtil which take multiple
> scans unnecessarily limit the types of the outputKeyClass and
> outputValueClass parameters, requiring them to extend WritableComparable and
> Writable respectively.
> In my specific use case, therefore, I cannot create a mapper job which
> outputs an hbase.client.Result.
> The methods in the MapReduce API to set map output key and value types do not
> impose this restriction.
> The other overloads of initTableMapperJob do not have this limitation - the
> restrictions were removed by https://issues.apache.org/jira/browse/HBASE-7024
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
