You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Dave Beech (JIRA)" <ji...@apache.org> on 2012/10/23 12:37:12 UTC
[jira] [Updated] (HBASE-7024) TableMapReduceUtil.initTableMapperJob
unnecessarily limits the types of outputKeyClass and outputValueClass
[ https://issues.apache.org/jira/browse/HBASE-7024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dave Beech updated HBASE-7024:
------------------------------
Attachment: HBASE-7024.patch
OK, thanks. Can I propose this patch - it simply removes the "extends Writable/WritableConfigurable" bit from the outputKeyClass and outputValueClass parameters
> 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: Bug
> Components: mapreduce
> Reporter: Dave Beech
> Priority: Minor
> 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