hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nikolai Grigoriev (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-16383) TableMapReduceUtil should allow using JobConf, not Job
Date Thu, 11 Aug 2016 15:55:20 GMT

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

Nikolai Grigoriev commented on HBASE-16383:

I know but I always assumed "mapred" package is for old API and mapreduce is for new one.
Thus, given the choice, I would go with new API for anything new. So with this improvement
request I am challenging the move from JobConf (old API) to Job (new API). I was trying to
search for the origin of that move but could not find any traces.

> 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

View raw message