[
https://issues.apache.org/jira/browse/NIFI-10815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17634030#comment-17634030
]
Paul Grey commented on NIFI-10815:
----------------------------------
Able to reproduce with processor `MonitorActivity`. Key to reproduce is to
avoid API call to "updateProcessor()". So the list of potential processors is:
- those that are annotated with `TriggerWithEmpty`
- those that can be started without interacting with `Processor Config` dialog
> Processor configuration issue (@TriggerWhenEmpty / Default Yield Duration)
> --------------------------------------------------------------------------
>
> Key: NIFI-10815
> URL: https://issues.apache.org/jira/browse/NIFI-10815
> Project: Apache NiFi
> Issue Type: Bug
> Reporter: Paul Grey
> Priority: Major
>
> While testing a custom processor with the annotation `TriggerWhenEmpty`,
> noted an issue with the scheduling of the processor.
> The processor setting `Yield Duration` defaults in the UI to `1 sec`. The
> expectation of the `onTrigger()` method is that, if the API
> `ProcessContext.yield()` is called, the processor should not be scheduled for
> the amount of time specified in Yield Duration.
> On adding the custom processor to the canvas and starting it, the processor
> is scheduled continuously. When the processor is stopped and Yield Duration
> is edited, starting the processor results in Yield Duration being honored.
> Reverting the edit (to set Yield Duration to the default) is also honored.
> It is as if the default Yield Duration setting is ignored when the setting
> has never been set.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
