ekovacs commented on issue #3351: NIFI-2933 Remote input/output ports at any PG URL: https://github.com/apache/nifi/pull/3351#issuecomment-477558039 Hi @ijokarumawak i checked out the PR and played around with it. There are a few remarks / questions i have: 1. any port dragged onto the root canvas is public by default. I only have the ability to select the type of the port if i am already in a PG. 2. if i create a simple, 2 part flow like this: a.) "generate flowfile" => "Remote Process Group" and b.) "input port" => "logAttribute" and then i want to group 'b.)' part of the flow into a PG, i'll get a: "Cannot move Ports from the Root Group to a Non-Root Group". i see that this limitation is not brought in by this PR, but existed previously in the master, along with some other checks: https://github.com/apache/nifi/blob/d3d43262db7fc5558a3a8a9c70926501ddb93e53/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/main/java/org/apache/nifi/groups/StandardProcessGroup.java#L2770 do we want to keep these limitations? 3. I create a PG, and in that PG i created a public port. Modified a.) part of the flow.: Disabled transmission. Deleted Connection. Created a new connection: "to input", selected the: "public port in child". Enabled transmission. FLowfiles started to flow to the PG's public port, this is good. While transitting, i created another connection: "to input" selected: "port-on-root-canvas". Flow files are being queued up for this connection. unless i stop transmission and start transmission for the Remote Process Group. see attached picture.  4. After 3., i deleted the connection with the queued flowfiles. RPG still shows "XYZ -> 2". yet it transmits only to one public port (one that is in the child PG) 
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
