In java action, you run your driver java code which launches MR job, right?
In that code, you will have a handle to the launched job and you can get
that job's counters as well

-Shwetha




On Mon, Jul 21, 2014 at 7:18 AM, Vishal Kapoor <[email protected]>
wrote:

> Thanks for the reply,
> Once you run MR with driver in Oozie as java action, how do we get the Job
> counters,
>
> Thanks,
> Vishal
>
>
> On Sat, Jul 19, 2014 at 12:11 AM, Harsh J <[email protected]> wrote:
>
> > Your driver code should ensure loading dependent jars into the
> > (subsequent) Job's dist-cache. In the HBase MR APIs, this is done via
> > the
> >
> https://hbase.apache.org/apidocs/org/apache/hadoop/hbase/mapreduce/TableMapReduceUtil.html#addDependencyJars(org.apache.hadoop.mapreduce.Job)
> > call.
> >
> > On Wed, Jul 16, 2014 at 3:08 AM, Vishal Kapoor
> > <[email protected]> wrote:
> > > I am using Oozie 3.3.2 and am stuck with Class not found when I run my
> > > HBase MR as java action, the jars are in the sharedLib as well as lib
> > under
> > > the workflow folder, but looks like the Mapper being the sub process of
> > the
> > > Java action(HBase MR) does not inherit the class.
> > >
> > > Looking for a workaround.
> > >
> > > Thanks,
> > > Vishal
> >
> >
> >
> > --
> > Harsh J
> >
>

-- 
_____________________________________________________________
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.

Reply via email to