[
https://issues.apache.org/jira/browse/NIFI-4170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16083420#comment-16083420
]
Y Wikander commented on NIFI-4170:
----------------------------------
I'll pursue your line of thinking.
The discussion turning to processor level misconfiguration makes me ponder the
Validators. Not that I really wanted to go deep into the weeds; but would
Validators be the "correct" way? Such that the processor would be stopped and
the yellow warning symbol would show up in the GUI.
This is presuming that Users would be more interested in pursuing those
(warning) messages vs. assumed transitory error messages that will probably go
away on their own (if you wait long enough).
To that end, can Validators be triggered _while_ a processor is running? And,
does a processor stop itself as part this action?
> PutWebSocket processor does not support 'Penalty duration' and 'Yield
> duration' settings
> ----------------------------------------------------------------------------------------
>
> Key: NIFI-4170
> URL: https://issues.apache.org/jira/browse/NIFI-4170
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Affects Versions: 1.3.0
> Reporter: Y Wikander
> Priority: Minor
> Labels: patch
> Attachments:
> 0002-websocket-PutWebSocket-processor-support-Penalty-dur.patch
>
>
> PutWebSocket processor does not support 'Penalty duration' and 'Yield
> duration' settings.
> I'm assuming that calling content.yield() will also cover 'Penalty duration'.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
