[
https://issues.apache.org/jira/browse/NIFI-1407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15105503#comment-15105503
]
Matt Burgess commented on NIFI-1407:
------------------------------------
IMO only the workarounds are confusing the types of operations. The Jira case
title is about the liveliness operations. In this case such a "run N times"
could be complementary to Timer/Cron, perhaps a decrementing count every time
the processor is scheduled. We could decouple it from the lifecycle operations
entirely, but then when a processor has run N times, it will no longer be
scheduled yet it will look like on the canvas that it is "alive". I think
automatically stopping the processor is a good compromise and makes the
functional state of the processor clear to the user. I haven't seen anyone
suggest removing the processor from the canvas, but if people are interested in
that then we should discuss it as well.
I'm not proposing my suggestions as the solution, rather using them to
illustrate some details we will have to deal with. I'm hoping the use cases
will give a more clear picture of how to proceed with a solution instead of
vice versa.
> Create a way to configure a processor to run only N times
> ---------------------------------------------------------
>
> Key: NIFI-1407
> URL: https://issues.apache.org/jira/browse/NIFI-1407
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Joseph Percivall
> Priority: Minor
>
> This is an issue that has arisen from multiple different users on the users
> thread. They would like a way to configure processors to run N times in order
> to facilitate one-time/initial-import scenario.
> The current work around is to set a very large time schedule time and then
> manually click start and then click stop.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
