[
https://issues.apache.org/jira/browse/NIFI-3422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15865966#comment-15865966
]
Joseph Witt commented on NIFI-3422:
-----------------------------------
This is a solid contribution/idea and a lot of details were uncovered and
address. Nice work! I do share Mark's view that the notion of run-once should
not be a scheduling strategy as in timer/event/cron but rather something that
can be invoked via the rest api to tell a presently stopped processor to be
scheduled, onTrigger invoked once, then unscheduled/stopped. In the UI this I
assume would show up as a right-click menu item. Having it as a scheduling
strategy along side the other scheduling strategies does not align with the
intent (allow the user to kick this thing off once to see what would happen)
and could lead to operational confusion.
> Run Once Scheduling
> -------------------
>
> Key: NIFI-3422
> URL: https://issues.apache.org/jira/browse/NIFI-3422
> Project: Apache NiFi
> Issue Type: New Feature
> Components: Core Framework, Core UI
> Affects Versions: 1.2.0
> Reporter: Nazario
> Priority: Minor
> Labels: features
> Fix For: 1.2.0
>
>
> A run once scheduling option allows a Processor to run once and then
> automatically stop. This is convenient when developing and debugging flows,
> or when building "visual scripts" for ad-hoc process integration or iterative
> analytics. Individual processors set to `Run once' can be selected on the
> canvas with a shift-click. Then clicking `Start' on the Operate Palette will
> start those processors which will run once and stop. Then one can modify
> processing parameters and repeat. Interactive analytics in particular
> benefit from this scheduling mode as they often require human review of
> results at the end of a flow followed by adjustment of flow parameters before
> running the next analytic flow.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
