The easy way out for jobs that require too much API-backed configuration would be to use a java action (with your custom driver) instead.
For porting the required configs onto the XML, for persisting with an MR action, you can use the job.getConfiguration().writeXml(…) call at end of driver (instead of submitting job) to have it prepare the XML and then extract the programmatically set values out of it to add to your workflow configuration. On Mon, Jul 14, 2014 at 6:41 AM, Vishal Kapoor <[email protected]> wrote: > Hello, > > I am using the following job configurations in my MapReduce job. > > job.setInputFormatClass(AvroKeyInputFormat.class); > job.setMapOutputKeyClass(ImmutableBytesWritable.class); > job.setMapOutputValueClass(Put.class); > > HFileOutputFormat.configureIncrementalLoad(job, table); > > How can I configure this in MR action? > > Thanks, > Vishal Kapoor -- Harsh J
