You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Micah Whitacre (JIRA)" <ji...@apache.org> on 2014/04/01 03:11:14 UTC

[jira] [Commented] (OOZIE-1767) Java Action automatically record child job ids

    [ https://issues.apache.org/jira/browse/OOZIE-1767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13955971#comment-13955971 ] 

Micah Whitacre commented on OOZIE-1767:
---------------------------------------

I actually poked through the code for the Hive action to look at how it solved this problem and I wonder if its solution could be applied to the Java action as well.  Essentially for any action it would scan the actions log files for any string which matches the jobId regex and then record those values into hadoop child properties file.

> 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)