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 *
