hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ted Yu (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-12929) TableMapReduceUtil.initTableMapperJob unnecessarily limits the types of outputKeyClass and outputValueClass
Date Tue, 27 Jan 2015 16:51:34 GMT

     [ https://issues.apache.org/jira/browse/HBASE-12929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Ted Yu updated HBASE-12929:
---------------------------
    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

Thanks for the patch, Will.

> 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: 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)

Mime
View raw message