nifi-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Joe Witt <joe.w...@gmail.com>
Subject Re: One-time Processors
Date Sun, 10 Jan 2016 20:37:00 GMT
Lars,

First, welcome to NiFi.

So you'll initiate the flow from NiFi through some manual trigger and
that part makes sense/sounds straightforward.  But then the question
is 'once the flow is done' I'd like it to shut down.  What are the
processors/things that begin the flow?  We've recently had someone
suggest adding a way to tell a processor to only run 'X' times before
being unscheduled and thus requiring manual start.  Sounds like that
might help you with your case as well.

There is little impact to having all the processors after the first
one running.  If there is no work to do they'll be quite efficient.

Do you think if a processor had a 'max executions' concept that it
would address your need?

Thanks
Joe

On Sun, Jan 10, 2016 at 3:32 PM, Lars Francke <lars.francke@gmail.com> wrote:
> Hi,
>
> I'm just getting started with Nifi and understand that I probably still have
> some misconceptions :)
>
> For various reasons I'd love to use NiFi for one-time actions/processors
> which I'd like to trigger as needed from the UI. I've seen the various
> scheduling strategies and the closest I've come is to have a really long run
> schedule or a specific cron schedule.
>
> What I'd really like is a way for a Processor to gracefully stop itself when
> it's done processing.
>
> Is there any way to achieve this?
>
> Thanks for your help

Mime
View raw message