You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Bryan Bende (JIRA)" <ji...@apache.org> on 2018/04/03 18:33:00 UTC
[jira] [Updated] (NIFI-5027) CLI - Add a command to start
controller services
[ https://issues.apache.org/jira/browse/NIFI-5027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bryan Bende updated NIFI-5027:
------------------------------
Assignee: Bryan Bende
Status: Patch Available (was: Open)
> CLI - Add a command to start controller services
> ------------------------------------------------
>
> Key: NIFI-5027
> URL: https://issues.apache.org/jira/browse/NIFI-5027
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Tools and Build
> Reporter: Pierre Villard
> Assignee: Bryan Bende
> Priority: Major
>
> When importing a versioned process group from the registry, all the components will be stopped (in case of update, only the newly added components will be stopped). We already have a command pg-start to start a process group, but it will fail if the process group relies on controller services that should be enabled first.
> A new command like pg-enable-cs could be added, or just add a parameter/flag to the pg-start command.
> Things to consider:
> * there can be a dependency chain between the controller services requiring to start the controller services in the right order. Example: the avro schema registry CS and a reader/writer CS depending on the schema registry CS.
> * there can be a CS defined at pg level that is not referenced by any component inside the pg but that would need to be started nevertheless. Example: the distributed map cache server CS.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)