[OOZIE-2631] Support both old and new Hadoop/HBase APIs with OozieActionConfigurator

• Type: Improvement
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Component/s: action
• Assignee: Unassigned
• Reporter: Nikolai Grigoriev
• Created: 11/Aug/16 17:01
• Updated: 11/Aug/16 17:01

Description

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 (introduced in SOC-1954). Unfortunately, this interface is using org.apache.hadoop.mapred.JobConf, not Job. In Hbase there are two classes: org.apache.hadoop.hbase.mapreduce.TableMapReduceUtil (new API) and org.apache.hadoop.hbase.mapred.TableMapReduceUtil (old API). New API is using org.apache.hadoop.mapreduce.Job everywhere where old API used JobConf. I believe it would be a good idea to improve the action configurator so it could accept either JobConf or Job. Maybe a way to go is to subclass OozieActionConfigurator and introduce a new interface like "OozieMapReduceActionConfigurator" that would provide configure() method accepting org.apache.hadoop.mapreduce.Job?

Issue Links

• is related to: OOZIE-1954 Add a way for the MapReduce action to be configured by Java code