[
https://issues.apache.org/jira/browse/HBASE-7024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13485297#comment-13485297
]
Hudson commented on HBASE-7024:
-------------------------------
Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #240 (See
[https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/240/])
HBASE-7024 TableMapReduceUtil.initTableMapperJob unnecessarily limits the
types of outputKeyClass and outputValueClass (Revision 1402710)
Result = FAILURE
stack :
Files :
*
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/mapred/TableMapReduceUtil.java
*
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/mapreduce/TableMapReduceUtil.java
> TableMapReduceUtil.initTableMapperJob unnecessarily limits the types of
> outputKeyClass and outputValueClass
> -----------------------------------------------------------------------------------------------------------
>
> Key: HBASE-7024
> URL: https://issues.apache.org/jira/browse/HBASE-7024
> Project: HBase
> Issue Type: Improvement
> Components: mapreduce
> Reporter: Dave Beech
> Priority: Minor
> Fix For: 0.96.0
>
> Attachments: HBASE-7024.patch
>
>
> The various initTableMapperJob methods in TableMapReduceUtil take
> outputKeyClass and outputValueClass parameters which need to extend
> WritableComparable and Writable respectively.
> Because of this, it is not convenient to use an alternative serialization
> like Avro. (I wanted to set these parameters to AvroKey and AvroValue).
> The methods in the MapReduce API to set map output key and value types do not
> impose this restriction, so is there a reason to do it here?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
