Cannot access input port in a process group?

[#1]

Hello this is a simple question.

Does anyone know why we cannot access an input port in a process group? I have a Remote Process Group trying to access an input port on another server that I have located in a Process Group but it doesn't appear when I try to connect to it with the connection to the Remote Process Group.

It'd be nice, since we will have many servers connecting to many Input Ports, to have them divided up into different process groups instead of all sprawled out on the main Nifi root interface.

[#2 · Accepted solution]

@Eric Lloyd

Input and Output ports are designed to send or receive data from one level up. When an input or output port is added at the root canvas level the one level up is another out of the system. You will also notice that ports added to the root canvas are rendered a little differently.

There is an open Apache Jira on this subject, feel free to add your comments and use case to it:

https://issues.apache.org/jira/browse/NIFI-2933

The current feeling is that adding Remote input and output ports should be left to the system administrator. This is because in a secured connection the admin must add the connecting systems as new users and authorize them to access these ports. Users are not typically granted this level of access.

Thanks,

Matt

[#3]

Thanks Matt.

[#4]

Not sure what your second comment meant if it was for me or not. I'm dealing with Nifi throughout the whole stack from the raw log files on a remote server through the Remote Process Group into the Input Port and into the HDFS. I guess that means I'm not a "user".