You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nifi.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2015/02/19 13:51:12 UTC

[jira] [Commented] (NIFI-363) Go to source/destination broken when source/destination is a Remote Process Group

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

ASF subversion and git services commented on NIFI-363:
------------------------------------------------------

Commit 57b5d589ad2c55394c2c96f53efd7e55a0e8c187 in incubator-nifi's branch refs/heads/NIFI-250 from [~mcgilman]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=57b5d58 ]

NIFI-363:
- Fixing 'Go to source' and 'Go to destination' when the component in question is a remote process group.

> Go to source/destination broken when source/destination is a Remote Process Group
> ---------------------------------------------------------------------------------
>
>                 Key: NIFI-363
>                 URL: https://issues.apache.org/jira/browse/NIFI-363
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Core UI
>    Affects Versions: 0.0.1
>            Reporter: Dan Bress
>            Assignee: Matt Gilman
>            Priority: Minor
>             Fix For: 0.0.2
>
>         Attachments: 0001-NIFI-363.patch
>
>
> If you have a Remote process group with a relationship between its output port and a processor, then click "go to source" on the relationship, you will get an error message saying the group could not be found.  At that point the UI gets in a funky state, you can move things around and the connections don't get updated.
> Same thing if you do "go to destination" on connections attached to input ports.



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