[
https://issues.apache.org/jira/browse/NIFI-1407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15105483#comment-15105483
]
Oleg Zhurakousky commented on NIFI-1407:
----------------------------------------
Joe
I think we can do better. IMHO Start/Stop are *lifecycle* operations of the
Processor. They control *liveliness* of the Processor. What this JIRA is
describing certain *functional characteristic* of a Processor that is *alive*.
So personally I would not mixed the two. The real life similarity would be a TV
that has to be plugged into the wall (alive) and then turned on (functioning).
On top of that think would what would happen to such Processor after it was
executed once. Should it remove itself from the canvas? What would trigger it
for the next initial import? So I think what we need to think about is adding
an additional trigger. Currently we provide Timer and Cron and we may need to
think of another type of Trigger or better of define an Trigger strategy and
expose it to end user for implementation so issues like this could be easily
solved in the future.
> 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)
