You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Aldrin Piri (JIRA)" <ji...@apache.org> on 2016/08/08 15:58:20 UTC
[jira] [Updated] (NIFI-2514) Update documentation on handling of
Controller Services
[ https://issues.apache.org/jira/browse/NIFI-2514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aldrin Piri updated NIFI-2514:
------------------------------
Fix Version/s: 1.0.0
> Update documentation on handling of Controller Services
> -------------------------------------------------------
>
> Key: NIFI-2514
> URL: https://issues.apache.org/jira/browse/NIFI-2514
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Documentation & Website
> Affects Versions: 1.0.0-Beta
> Reporter: Aldrin Piri
> Fix For: 1.0.0
>
>
> 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.
> {quote}
> 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?
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)