Hello, 1) Currently remote ports still need to be on the root canvas.
2) Hard to say the limit, but you will be bound the number of TCP connections you can create and how many threads can handle them. 3) You could still use process groups to enclose the flow of the template, and inside the process group would be a regular input port, then when this template is instantiated you assign the correct permissions to the process group, and some user who has permissions to the root canvas makes the connection from the remote input port on the root canvas, into the regular input port inside the process group. Thanks, Bryan On Wed, Feb 28, 2018 at 8:47 AM, <mohit.j...@open-insights.co.in> wrote: > Hi all, > > > > I have a few query regarding NiFi cluster mode:- > > Nifi 1.4.0 doesn’t allow to edit a remote process group which is overcome in > NiFi 1.5.0. So we are planning to move to nifi 1.5.0. Is it necessary to use > the remote input ports in the root canvas? We used to initialize the > templates in a process group. But remote input ports are not supported in > the root canvas only. Is this the case with NiFi 1.5.0 as well? > Is there any limit of remote process group in nifi cluster mode? :- I am > planning to create templates using remote process groups which points to the > same URL. How many such remote process groups can be created. > If it is possible to design in above two ways, how to secure it? We had a > plan to secure a process group for different users. What would be the best > approach in this case? As for each template we have two process groups, a > remote input port and a remote process group in the root canvas. > > > > Regards, > > Mohit Jain > >
