Hi Mona, Thanks for the info. I was working on getting monitoring info for oozie in chukwa. I see OozieClient has a bunch of helpful APIs to get the info but did not include this instrumentation information.
Just wondering if we can make getting the instrumentation info using a simple call, like oozieClient.getInstrumentationInfo() instead of writing a REST Client. Further, the same code can be used while wrapping in AuthOozieClient in kerberos setup. Apart from this, I don't have any reason to include this info. On Mon, Apr 7, 2014 at 10:39 AM, Mona Chitnis <[email protected]> wrote: > There wasn¹t a use-case so far for fetching instrumentation info directly > via Java Code or CLI, which would be enabled by an implementing method in > OozieClient. So far, this API is mostly used via REST API by, for example, > Oozie web-console and other services using this hook for monitoring Oozie > service. > > So there is no strong reason not to implement it in OozieClient, there was > simply no need to expose multiple ways to access same info. > > How are you using this API in your case? > > > On 4/4/14, 11:51 PM, "Sreepathi" <[email protected]> wrote: > > >Hello, > > > >I was looking into OozieClient.java file. I don't see instrumentation > >( oozie/v1/admin/instrumentation) > >method being there. Is this intentional ? > > > >Of course we can submit the REST call to get the info, but was curious to > >know why wasn't this part of this class. > > > >-- > >*Regards,* > >--- *Sreepathi * > > -- *Regards,* --- *Sreepathi *
