[jira] [Commented] (NIFI-6821) "Off-Page" Input/Output Ports
[ https://issues.apache.org/jira/browse/NIFI-6821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16962825#comment-16962825 ] Keith Hinde commented on NIFI-6821: --- Thanks for the quick feedback - great to hear it's in the mix somewhere. I'll close this one as a duplicate and also because "Wormhole Connections" sounds much cooler! > "Off-Page" Input/Output Ports > - > > Key: NIFI-6821 > URL: https://issues.apache.org/jira/browse/NIFI-6821 > Project: Apache NiFi > Issue Type: Wish > Components: Core UI >Reporter: Keith Hinde >Priority: Minor > > When you have complex nested flows, together with a need to be as modular as > possible, you can end up with quite a tangled nest of input/output ports > joining several layers of flows. This can get very messy, very quickly. > Alternatively you add complexity by using remote process groups or listenhttp > to allow hops between distinct process groups. Again, less than desirable. > Is it feasible to change the input/output port facility to allow linkage to > ports in other flows, not just parent or child? Something like off page > connectors in Visio? In this way, you tidy things up a lot and also avoid > introducing remote functionality you don't really need? -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (NIFI-6821) "Off-Page" Input/Output Ports
[ https://issues.apache.org/jira/browse/NIFI-6821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16962190#comment-16962190 ] Joe Witt commented on NIFI-6821: I think definitely yes that is the ask. I'd also say we totally need to do this at some point as it would help simplify flow setup for large/complex flows. But lots and lots of good things to improve > "Off-Page" Input/Output Ports > - > > Key: NIFI-6821 > URL: https://issues.apache.org/jira/browse/NIFI-6821 > Project: Apache NiFi > Issue Type: Wish > Components: Core UI >Reporter: Keith Hinde >Priority: Minor > > When you have complex nested flows, together with a need to be as modular as > possible, you can end up with quite a tangled nest of input/output ports > joining several layers of flows. This can get very messy, very quickly. > Alternatively you add complexity by using remote process groups or listenhttp > to allow hops between distinct process groups. Again, less than desirable. > Is it feasible to change the input/output port facility to allow linkage to > ports in other flows, not just parent or child? Something like off page > connectors in Visio? In this way, you tidy things up a lot and also avoid > introducing remote functionality you don't really need? -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (NIFI-6821) "Off-Page" Input/Output Ports
[ https://issues.apache.org/jira/browse/NIFI-6821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16962186#comment-16962186 ] Mark Payne commented on NIFI-6821: -- I believe what you are talking about here is the same as what is outlined in this feature proposal: [https://cwiki.apache.org/confluence/display/NIFI/Wormhole+Connections] Is that accurate? > "Off-Page" Input/Output Ports > - > > Key: NIFI-6821 > URL: https://issues.apache.org/jira/browse/NIFI-6821 > Project: Apache NiFi > Issue Type: Wish > Components: Core UI >Reporter: Keith Hinde >Priority: Minor > > When you have complex nested flows, together with a need to be as modular as > possible, you can end up with quite a tangled nest of input/output ports > joining several layers of flows. This can get very messy, very quickly. > Alternatively you add complexity by using remote process groups or listenhttp > to allow hops between distinct process groups. Again, less than desirable. > Is it feasible to change the input/output port facility to allow linkage to > ports in other flows, not just parent or child? Something like off page > connectors in Visio? In this way, you tidy things up a lot and also avoid > introducing remote functionality you don't really need? -- This message was sent by Atlassian Jira (v8.3.4#803005)
