You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Matt Gilman (JIRA)" <ji...@apache.org> on 2018/05/31 13:44:00 UTC

[jira] [Commented] (NIFI-5255) UI - ability to connect multiple output ports to one input port

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

Matt Gilman commented on NIFI-5255:
-----------------------------------

As a workaround while the use case is evaluated, have you considered using a funnel to merge the different sources into two output ports for A, B, C and for B, C, D?

> UI - ability to connect multiple output ports to one input port
> ---------------------------------------------------------------
>
>                 Key: NIFI-5255
>                 URL: https://issues.apache.org/jira/browse/NIFI-5255
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Core UI
>            Reporter: Pierre Villard
>            Priority: Major
>
> At the moment, when connecting two process groups, it's only possible to have 1-to-1 relationships to connect one output port to one input port.
> Here is my use case: I've one common process group collecting logs from multiple sources (A, B, C, D) and two process groups to process the logs. One of the process group should only process logs from A, B, C while the other should process logs from B, C, D.
> In the common process group, I've one output port per source (A, B, C, D). In each "processing" process group, I've one single input port (and I'll re-route if necessary based on the source). At the moment, I have to drag 6 relationships to connect the common process group to the two others. I'd like to only draw 2 connections. When dragging the connection, I should be able to select multiple output ports from the common PG for one single destination. That would make the workflow easier to understand, and this approach much more scalable.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)