[ https://issues.apache.org/jira/browse/NIFI-5027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pierre Villard updated NIFI-5027: --------------------------------- Resolution: Fixed Fix Version/s: 1.7.0 Status: Resolved (was: Patch Available) > 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 > Fix For: 1.7.0 > > Attachments: TestStartStopCS.xml > > > 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)