Hello Mark and Joe,
Thank you very much for your replies. This explains the behaviour we have been seeing. The hint to look for the Operate palette instead of the top right corner made the difference [😉] Best regards, Panos ________________________________ From: Mark Payne <[email protected]> Sent: Thursday, November 17, 2016 3:16 PM To: [email protected] Subject: Re: Controller services visibility problem Hi Panos, You are correct in that Controller Services that are created in the top-right corner will not be available to Processors. These are "controller-level" services and are available only to Reporting Tasks and other Controller Services. If you want to use a Controller Service for Processors, then you need to create the service at the Process Group level (in the Operate palette). A Controller Service that is created here is available to any Processor in this group and any child group. So if you want a Controller Service to be available to all Processors, you can simply create the Controller Service at the Root Process Group, and all child groups will then have access to it. Thanks -Mark On Nov 17, 2016, at 9:10 AM, Panos Geo <[email protected]<mailto:[email protected]>> wrote: Hello all, We are using NiFi 1.0 over http without any authentication, so all our users are coming to NiFi as anonymous. The problem we are having is of controller services visibility. So if we create a controller service (say database connection) from the top right option of the canvas, this is not visible within a group of processors. Also the contrary is also true, if we create a controller service for a group of processors, this is not visible to the rest of the canvas. Is there a way to assign visibility for a controller service, e.g. set global visibility for a service, so that we don’t have to recreate it in all the groups of processors that need it? As a side note, we didn't have this problem with NiFi versions before 1.0. Many thanks, Panos
