Re: Why the Input Ports are not allowed to be inside the ProcessorGroups

2016-01-21 Thread Matt Gilman
Paresh, Also wanted to let you know another upcoming feature is our multi-tenant data flow [1]. One of the concepts being considered is creating separate workspaces. This would essentially offer multiple root level Process Groups that could provide different levels of authorization. This could pot

Re: Why the Input Ports are not allowed to be inside the ProcessorGroups

2016-01-21 Thread Matt Gilman
Paresh, Input/Output ports are allowed to be inside of Process Groups. These facilitate data flow in between the Process Group and it's parent Process Group. In the case of the root Process Group, it facilitates remote data flows with other NiFi instances (or anything that can speak the site-to-si

Why the Input Ports are not allowed to be inside the ProcessorGroups

2016-01-21 Thread Paresh Shah
In our use case to keep the UI managable we create different ProcessorGroups for the different pipelines. But when using the RemoteProcessorGroups and InputPorts we are forced to move the pipelines out of the processor groups and into the root canvas. This helps us tear down and do the deploymen