Thanks @Vishwakarma ! 2015-11-05 14:36 GMT+08:00 Jaydeep Vishwakarma < [email protected]>:
> You can use oozie.launcher.action.main.class. > > Look at this example. > > > https://github.com/apache/oozie/blob/master/examples/src/main/apps/custom-main/workflow.xml > > On Thu, Nov 5, 2015 at 9:31 AM, 王猛 <[email protected]> wrote: > > > Hi , I used *old mapreduce API* in oozie , it failed with : > > > > Caused by: java.lang.RuntimeException: java.lang.RuntimeException: *class > > VipTrackingMapper not org.apache.hadoop.mapred.Mapper* > > at org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2079) > > at org.apache.hadoop.mapred.JobConf.getMapperClass(JobConf.java:1109) > > at org.apache.hadoop.mapred.MapRunner.configure(MapRunner.java:38) > > > > > > > > However, when I do the following setting : > > > > > > *1. change mapred.mapper.class to mapreduce.map.class2. set > > mapred.mapper.new-api=false3. set mapred.reducer.new-api=false* > > It failed with : > > > > Failing* Oozie Launcher, Main class > > [org.apache.oozie.action.hadoop.MapReduceMain], main() threw exception, > > mapreduce.job.map.class is incompatible with map compatability mode.* > > java.io.IOException: mapreduce.job.map.class is incompatible with map > > compatability mode. > > at org.apache.hadoop.mapreduce.Job.ensureNotSet(Job.java:1199) > > at org.apache.hadoop.mapreduce.Job.setUseNewAPI(Job.java:1235) > > at org.apache.hadoop.mapreduce.Job.submit(Job.java:1288) > > at org.apache.hadoop.mapred.JobClient$1.run(JobClient.java:564) > > > > *Is there any way can let oozie support old mapreduce API ? thanks.* > > > > -- > _____________________________________________________________ > The information contained in this communication is intended solely for the > use of the individual or entity to whom it is addressed and others > authorized to receive it. It may contain confidential or legally privileged > information. If you are not the intended recipient you are hereby notified > that any disclosure, copying, distribution or taking any action in reliance > on the contents of this information is strictly prohibited and may be > unlawful. If you have received this communication in error, please notify > us immediately by responding to this email and then delete it from your > system. The firm is neither liable for the proper and complete transmission > of the information contained in this communication nor for any delay in its > receipt. >
