hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Will Temperley (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-7024) TableMapReduceUtil.initTableMapperJob unnecessarily limits the types of outputKeyClass and outputValueClass
Date Mon, 26 Jan 2015 13:14:34 GMT

    [ https://issues.apache.org/jira/browse/HBASE-7024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14291802#comment-14291802
] 

Will Temperley commented on HBASE-7024:
---------------------------------------

This is marked as fixed, but the unnecessary restrictions on the types of outputKeyClass and
outputValueClass are still in place.

> 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.95.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 was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message