[
https://issues.apache.org/jira/browse/NIFI-4200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16094766#comment-16094766
]
ASF GitHub Bot commented on NIFI-4200:
--------------------------------------
Github user trixpan commented on the issue:
https://github.com/apache/nifi/pull/2022
@pvillard31 - I assume the processor should be able to control nifi
components only. Should we rename it to make this explicit?
> Consider a ControlNiFi processor
> --------------------------------
>
> Key: NIFI-4200
> URL: https://issues.apache.org/jira/browse/NIFI-4200
> Project: Apache NiFi
> Issue Type: New Feature
> Components: Extensions
> Reporter: Pierre Villard
> Assignee: Pierre Villard
>
> We frequently see on the mailing list the need to start/stop a processor
> based on incoming flow files. At the moment, that's something that can be
> scripted or that can be done using multiple InvokeHttp processors but it
> requires a bit of work.
> Even though it is not really in the "NiFi way of thinking", it would be
> interesting to have a processor with the following parameters:
> - NiFi REST API URL
> - Username
> - Password
> - Processor UUID (with expression language)
> - Action to perform (START, STOP, START/STOP, STOP/START)
> - Sleep duration (between the START and STOP calls when action is START/STOP,
> or STOP/START)
> That would be helpful in use cases like:
> - start a workflow based on another workflow
> - start a processor not accepting incoming relationship based on a flow file
> - restart a processor to "refresh" its configuration when the processor
> relies on configuration files that could be changed
> - have a "start once" behavior
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
