You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@hbase.apache.org by "Andrew Kyle Purtell (Jira)" <ji...@apache.org> on 2022/06/16 01:25:00 UTC

[jira] [Resolved] (HBASE-14833) HFileOutputFormat2 should allow for custom reducer logic

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

Andrew Kyle Purtell resolved HBASE-14833.
-----------------------------------------
    Resolution: Not A Problem

> HFileOutputFormat2 should allow for custom reducer logic
> --------------------------------------------------------
>
>                 Key: HBASE-14833
>                 URL: https://issues.apache.org/jira/browse/HBASE-14833
>             Project: HBase
>          Issue Type: Improvement
>          Components: API, mapreduce
>            Reporter: Gowtam Lal
>            Priority: Minor
>
> Right now, HFileOutputFormat2.configureIncrementalLoad() will configure a ReducerClass which takes all input and passes it through to be written to an HFile. Unfortunately, this prevents a user from plugging in his or her own logic for the Reduce phase. 
> TableMapReduceUtil.initTableReducerJob() accepts a custom ReducerClass, allowing users to operate on the tuples coming out of the MapperClass before they're written to output. Could HFileOutputFormat2.configureIncrementalLoad() possibly do something similar?



--
This message was sent by Atlassian Jira
(v8.20.7#820007)