I absolutely agree that the execution data should've been more easily exposed via client API. Currently the JavaActionExecutor reads from a file that stores the action's output props, and again sets it to the context as "context.setExecutionData(SUCCEEDED, props);"
Is what you're looking for, an API to fetch the properties corresponding to all 'status' states, given the action or context as argument? Or are you looking for visibility only via the GUI, the way Hue is providing to some extent? -- Mona On 7/15/13 9:57 AM, "Alexander Taggart" <[email protected]> wrote: >I discovered that Hue exposes the ExecutionData, but unfortunately it is >terribly mangled since Oozie's API takes a Properties object, which at >some >point is converted into a java string, and then Hue prints that string >with >escapes (i.e., one big string littered with \n). > > > >On Sun, Jul 14, 2013 at 11:04 PM, Harsh J <[email protected]> wrote: > >> Additionally, you may be looking for >> https://issues.apache.org/jira/browse/OOZIE-864 >> >> On Sat, Jul 13, 2013 at 4:05 AM, Mona Chitnis <[email protected]> >> wrote: >> > Hi Alexander, >> > >> > Maybe you would want to log it via the custom action executor class >>and >> > refer to logs via UI? >> > >> > -- >> > Mona >> > >> > On 7/12/13 9:54 AM, "Alexander Taggart" <[email protected]> wrote: >> > >> >>I have a custom action executor that >> >>invokes >> >>>>org.apache.oozie.action.ActionExecutor.Context.setExecutionData(String, >> >>Properties) upon completion. I cannot find any way to access that >>data >> >>through the oozie console. >> > >> >> >> >> -- >> Harsh J >>
