[
https://issues.apache.org/jira/browse/OOZIE-1767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13960499#comment-13960499
]
Micah Whitacre commented on OOZIE-1767:
---------------------------------------
With Crunch we have a way of getting the JobIds off of the execution the
problem is there is no clear API or means for something launched through the
Java Action to publish the child processes without rolling their own action.
The idea of this enhancement was to avoid several permutations of the same
action with the only difference being how the child ids are reported.
> Java Action automatically record child job ids
> ----------------------------------------------
>
> Key: OOZIE-1767
> URL: https://issues.apache.org/jira/browse/OOZIE-1767
> Project: Oozie
> Issue Type: Improvement
> Components: action
> Reporter: Micah Whitacre
>
> It is common for consumers to utilize Big Data frameworks like Crunch and
> Cascading inside of their larger processing workflows. These frameworks when
> ran will launch potentially one to many MR jobs. The common way to launch
> these is using the Java action as both frameworks have a specific API for
> launching and executing the jobs. Unfortunately for the default Java action,
> those spawned processes are not tied to the Oozie action which launched them.
> It would be great if there was a way for jobs launched from the Java action
> to be tied back to the Oozie action.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
