> Using Oozie seems to be an overkilling for this application, besides, it
doesn't support "loops"
> so the recusrsion can't really be implemented.

Correct, Oozie does not support loops, this is a restriction by design
(early prototypes supported loops). The idea was that you didn't want never
ending workflows. To this end, Coordinator Jobs address the recurrent run
of workflow jobs.

Still, if you want to do recursion in Oozie, you certainly can, a workflow
invoking to itself as a sub-workflow. Just make sure you define properly
your exit condition.

If you have additional questions, please move this thread to the
u...@oozie.apache.org alias.


Thx


On Tue, Nov 27, 2012 at 4:03 AM, Zoltán Tóth-Czifra <
zoltan.tothczi...@softonic.com> wrote:

>  Hi everyone,
>
>  Thanks in advance for the support. My problem is the following:
>
>  I'm trying to develop a fairly complex MapReduce application using the
> streaming API (for demonstation purposes, so unfortunately the "use Java"
> answer doesn't work :-( ). I can get one single MapReduce phase running
> from command line with no problem. The problem is when I want to add more
> MapReduce phases which use each others output, and I maybe even want to do
> a recursion (feed the its output to the same phase again) conditioned by a
> counter.
>
>  The solution in Java MapReduce is trivial (i.e. creating multiple Job
> instances and monitoring counters) but with the streaming API not quite.
> What is the correct way to manage my application with its native code?
> (Python, PHP, Perl...) Calling shell commands from a "controller" script?
> How should I obtain counters?...
>
>  Using Oozie seems to be an overkilling for this application, besides, it
> doesn't support "loops" so the recusrsion can't really be implemented.
>
>  Thanks a lot!
> Zoltan
>



-- 
Alejandro

Reply via email to