[ 
https://issues.apache.org/jira/browse/NIFI-2597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15427060#comment-15427060
 ] 

ASF GitHub Bot commented on NIFI-2597:
--------------------------------------

GitHub user mcgilman opened a pull request:

    https://github.com/apache/nifi/pull/895

    Addressing issue preventing creation of a self loop

    NIFI-2597:
    - Updating the correct object when attempting to create a self loop.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/mcgilman/nifi NIFI-2597

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/nifi/pull/895.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #895
    
----
commit aa31a8bbc5413681fbfff095d76d9aeaa9290b67
Author: Matt Gilman <[email protected]>
Date:   2016-08-18T19:53:06Z

    NIFI-2597:
    - Updating the correct object when attempting to create a self loop.

----


> Unable to create self-loop connection from existing connection
> --------------------------------------------------------------
>
>                 Key: NIFI-2597
>                 URL: https://issues.apache.org/jira/browse/NIFI-2597
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Core UI
>            Reporter: Mark Payne
>            Assignee: Matt Gilman
>             Fix For: 1.0.0
>
>
> If I have a connection that goes from Processor A to Processor B (both 
> stopped), and then I drag the destination of the connection from Processor B 
> to Processor A, so that it is a self-loop for Processor A, the connection 
> stays connected to Processor B. The UI doesn't create the multiple 
> bend-points on the connection but does appear to make the connection 
> self-looping. When I click on the 'blue dot' on the connection that 
> represents its destination, the connection is re-drawn to go to the 
> destination.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to