[ 
https://issues.apache.org/jira/browse/NIFI-2410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15421863#comment-15421863
 ] 

Sarah Olson commented on NIFI-2410:
-----------------------------------

Adding comment from 2515 for additional context:

Controller services work as anticipated but the way they are structured is a 
bit of a departure from how they used to work. Would be helpful to have docs 
that inform users of how each is structured.
It seems that Flow Controller level controller services are only there for 
other controller services and/or reporting tasks.
These are separate from controller services that are for an associated process 
group (or parent) which are nested.


The access/visibility of controller services seems a bit confusing to me and 
don't see any docs that clarify. It seems that for nested process groups, I can 
view all controller services in parent process groups. The configuration on the 
"Operate" palette seems to control these which seems to be completely disjoint 
from the flow level controller settings, which are not listed in any of the 
nested process groups. I would imagine the flow level controller settings would 
also be present in each of the child PGs regardless of nesting level but these 
do not seem to be visible to any of my components. Are these just to support 
reporting tasks? Would reporting tasks also have a similar hierarchy where they 
could also be contained within a given PG chain?

> Document controller service display
> -----------------------------------
>
>                 Key: NIFI-2410
>                 URL: https://issues.apache.org/jira/browse/NIFI-2410
>             Project: Apache NiFi
>          Issue Type: Task
>          Components: Core Framework
>    Affects Versions: 1.0.0
>            Reporter: Haimo Liu
>            Assignee: Sarah Olson
>            Priority: Critical
>             Fix For: 1.0.0
>
>         Attachments: Screen Shot 2016-07-26 at 10.36.08 PM.png, Screen Shot 
> 2016-07-26 at 10.57.19 PM.png, Screen Shot 2016-07-26 at 11.05.42 PM.png
>
>
> NIFI 1.0 snapshot, 7/26 build, didn't turn on internal authorization/policy 
> management, running in a clustered mode (3-node).
> Group level CS display seems inconsistent
> 1. hamburger menu -> Controller Settings -> Controller Services, can see one 
> CS (no matter which PG i am in, can always see this single CS, 
> "DBCPConnectionPool", see attached image) this CS is only referenceable by 
> Reporting Tasks, NOT by any processors
> 2. Select a PG where I have the GenerateTableFetch processor, click the 
> "Configuration" icon in "Operate panel", can see five different controller 
> services here, these are all PG level CS. Select nothing (click the canvas), 
> click the "Configuration" icon in "Operate panel", can see two different 
> controller services here, these are root level CS
> in NIFI 1.0, we need to document the difference between CS that are 
> referenceable by processors. vs that are only referenceable by reporting tasks



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to