[
https://issues.apache.org/jira/browse/NIFI-810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14708601#comment-14708601
]
Mark Payne commented on NIFI-810:
---------------------------------
[~aldrin]: I definitely agree. In fact, I'd take it one step further and
recommend that if a Processor has that annotation, the UI should not even allow
a user to create a connection with that Processor as the target. If a
connection already exists (because it was created before such a capability was
implemented, I would recommend we just mark the Processor invalid. I could have
sworn we had a ticket for this, but I can't find it. Maybe I just dreamed it :)
> Create Annotation that indicates that a Processor cannot be scheduled to run
> without an incoming connection
> -----------------------------------------------------------------------------------------------------------
>
> Key: NIFI-810
> URL: https://issues.apache.org/jira/browse/NIFI-810
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Reporter: Mark Payne
>
> Currently, if a Processor has no incoming connections but is started, it will
> continually without ever accomplishing anything. We should have an
> annotation, perhaps @RequiresInput, that indicates that the Processor should
> not be scheduled to run unless it has an incoming connection.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
