[
https://issues.apache.org/jira/browse/NIFI-1777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15245446#comment-15245446
]
ASF GitHub Bot commented on NIFI-1777:
--------------------------------------
Github user olegz commented on the pull request:
https://github.com/apache/nifi/pull/357#issuecomment-211322321
Was able to validate that when/if someone attempts to delete a connected
processor a window pops up with the error message "Destination of Connection
(LogAttribute[id=7a37a5bb-1017-4732-8c31-a6c1f44eea18]) is running". So all
good, adequate tests provided, +1.
@mcgilman @scottyaslan perhaps in the future we can further address it (as
an additional feature) in the UI and disable "Delete" option all together.
> 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
> Assignee: Pierre Villard
> Priority: Minor
> Fix For: 1.0.0, 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)
