[
https://issues.apache.org/jira/browse/NIFI-1777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15243000#comment-15243000
]
Bryan Bende commented on NIFI-1777:
-----------------------------------
[~pvillard] you are right, I tried it again, and it appears that you can stop
it. So I guess the issue is just that you shouldn't be able to delete a
connection going to a running processor, because a processor should never be
running in an invalid state.
For what it is worth, you can make this happen with any two processors, but it
is only obvious on processors that have @TriggerWhenEmpty because you will see
the tasks increasing even when there is no incoming connection.
> Incoming Connection Deleted While Processor Still Running
> ---------------------------------------------------------
>
> Key: NIFI-1777
> URL: https://issues.apache.org/jira/browse/NIFI-1777
> Project: Apache NiFi
> Issue Type: Bug
> Affects Versions: 0.6.0, 0.6.1
> Reporter: Bryan Bende
> Priority: Minor
> Fix For: 0.7.0
>
>
> I created a simple flow with ExecuteCommand connected to PutKafka. I had
> PutKafka running and ExecuteCommand stopped, and then deleted ExecuteCommand.
> At this point PutKafka showed a bulletin for being invalid because it
> requires an incoming connection, but PutKafka was still running and couldn't
> be stopped until adding back an incoming connection.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
