[
https://issues.apache.org/jira/browse/OOZIE-1908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Micah Whitacre updated OOZIE-1908:
----------------------------------
Attachment: OOZIE-1908.patch
Here's a stab in the dark at what this action might look like. It is by no
means functional or merge ready but should show the direction I was thinking.
It does require a common launching class being added to crunch so that
consumers would start using that API and therefore make reporting child job ids
easier.
> Create Crunch Action
> --------------------
>
> Key: OOZIE-1908
> URL: https://issues.apache.org/jira/browse/OOZIE-1908
> Project: Oozie
> Issue Type: New Feature
> Components: action
> Reporter: Micah Whitacre
> Attachments: OOZIE-1908.patch
>
>
> Launching an Apache Crunch Pipeline[1] is currently done through the Java
> Action. While this works it, it however loses traceability between the
> action and any child processes that get launched.
> [1] - http://crunch.apache.org/
--
This message was sent by Atlassian JIRA
(v6.2#6252)
