You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Sean Busbey (JIRA)" <ji...@apache.org> on 2016/08/11 15:28:20 UTC

[jira] [Commented] (HBASE-16383) TableMapReduceUtil should allow using JobConf, not Job

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

Sean Busbey commented on HBASE-16383:
-------------------------------------

The mapred version already uses JobConf. Take a look at [org.apache.hadoop.hbase.mapred.TableMapReduceUtil|https://github.com/apache/hbase/blob/rel/1.2.2/hbase-server/src/main/java/org/apache/hadoop/hbase/mapred/TableMapReduceUtil.java].

> TableMapReduceUtil should allow using JobConf, not Job
> ------------------------------------------------------
>
>                 Key: HBASE-16383
>                 URL: https://issues.apache.org/jira/browse/HBASE-16383
>             Project: HBase
>          Issue Type: Improvement
>          Components: util
>            Reporter: Nikolai Grigoriev
>            Priority: Minor
>
> I was recently trying to set up an MR job initialized with TableMapReduceUtil to be ran by Oozie. Oozie offers a way to configure the job by providing an implementation of org.apache.oozie.action.hadoop.OozieActionConfigurator. Unfortunately, this interface is using org.apache.hadoop.mapred.JobConf, not Job. I may be wrong but I believe that everything TableMapReduceUtil does actually maps to the job configuration so it does not really need the Job itself. If this is true, probably it would be more appropriate to use JobConf in TableMapReduceUtil instead of Job? Or provide the methods for both.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)