Support Questions
Find answers, ask questions, and share your expertise
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.

Controller services created from Controller Settings menu are not available to processors and vice versa

Solved Go to solution

Controller services created from Controller Settings menu are not available to processors and vice versa

Rising Star

Hello,

In our NiFi instance (1.2.0) we're finding that controller services created from the Controller Settings menu (top right corner in the UI) are not visible/accessible when you try to look for them through a processor; for example, after a HiveConnectionPool Controller service is created through the controller settings menu, it does not show up in PutHiveinQL's "Hive Database Connection Pooling Service" drop down values; also, when a new Controller service is created by selecting the "Create new service..." option from the dropdown values in PutHiveQL processor, that controller service does not show up in the Controller services listing (accessed through the Controller Settings menu).

39903-screen-shot-2017-10-20-at-94216-am.png

39904-screen-shot-2017-10-20-at-94233-am.png

It seem like it is something to do with user access permissions in the UI; if yes, how can this be corrected.

I'm not familiar with the user access permissions settings, our Admin handles that.

Thanks.

1 ACCEPTED SOLUTION

Accepted Solutions

Re: Controller services created from Controller Settings menu are not available to processors and vice versa

Hi @Raj B

This is the expected behavior. The controller services that you add from the Hamburger menu (top right) are used only for reporting tasks.

If you want to add controller services for processor you should add them from the configure menu of your process group or root canvas.

This article explains the difference : https://community.hortonworks.com/articles/90259/understanding-controller-service-availability-in-a....

4 REPLIES 4

Re: Controller services created from Controller Settings menu are not available to processors and vice versa

Hi @Raj B

This is the expected behavior. The controller services that you add from the Hamburger menu (top right) are used only for reporting tasks.

If you want to add controller services for processor you should add them from the configure menu of your process group or root canvas.

This article explains the difference : https://community.hortonworks.com/articles/90259/understanding-controller-service-availability-in-a....

Re: Controller services created from Controller Settings menu are not available to processors and vice versa

Rising Star
@Abdelkrim Hadjidj

Thanks for clarifying. It would have been nicer to let the controller services be accessible throughout the UI, regardless of where they were created.

Re: Controller services created from Controller Settings menu are not available to processors and vice versa

Guru

Services defined in the Controller Settings are available to Reporting Tasks and other services defined there. Services defined within a Process Group are available to descendent components.

To create a service that is available to all components in the flow, define it in the root Process Group. Here is a helpful article on the scoping of Controller services:

https://community.hortonworks.com/content/kbentry/90259/understanding-controller-service-availabilit...

Improvements were also made in the documentation in version 1.3.0:

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

In version 1.4.0, the name of the tab was changed to be more explicit as well to "Reporting Task Controller Services".

Re: Controller services created from Controller Settings menu are not available to processors and vice versa

Rising Star

@Andrew Lim thanks for clarifying further.

Don't have an account?
Coming from Hortonworks? Activate your account here