So a bit ago I logged OOZIE-1767[1] to help track child jobs that would be launched from running Crunch or Cascading code inside of an Oozie Java action. Oozie currently only tracks the job ids of the launching job and not the ids of the jobs that might get spawned. So while the suggestion on the issue is not necessarily the right solution it got me thinking about whether or not tracking the child jobs would even be able to solve what I was looking for.
I'm curious where are those child job ids stored? Are they retrievable or are they only usable as a parameter/property inside of the workflow instance? (e.g. inside of the workflow spec). Or is that information stored in a way that I could retrieve it later from Oozie using something like the REST API[2]? [1] - https://issues.apache.org/jira/browse/OOZIE-1767 [2] - http://oozie.apache.org/docs/3.3.2/WebServicesAPI.html#Job_Information
