[
https://issues.apache.org/jira/browse/MINIFICPP-1999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17641127#comment-17641127
]
Gábor Gyimesi commented on MINIFICPP-1999:
------------------------------------------
"by passing the command and the name of the processor (it's strange that you
can't pass its uid))"
Regarding this comment UUID can also be used to start/stop a component in the
latest version of MiNiFi. This was implemented in the following change:
[https://github.com/apache/nifi-minifi-cpp/pull/1388] It will be available in
the 0.13.0 release.
> Persistent state of processors
> ------------------------------
>
> Key: MINIFICPP-1999
> URL: https://issues.apache.org/jira/browse/MINIFICPP-1999
> Project: Apache NiFi MiNiFi C++
> Issue Type: New Feature
> Affects Versions: 0.12.0
> Reporter: Kondakov Artem
> Priority: Major
> Fix For: 0.14.0
>
>
> Hi
> In apache/nifi each processor can be started and stopped. It is also possible
> to activate and deactivate. In this case, the state of the processors is
> saved when the application is restarted.
> minifi-cpp also has the ability to start and stop individual processors using
> the C2 protocol or minificontroller (by passing the command and the name of
> the processor (it's strange that you can't pass its uid))
> However, after restarting minifi all the same, all processors start, while
> the permanent state store is configured
>
> {color:#172b4d}nifi.state.management.provider.local.path=./repositories/componentstate{color}
> {color:#00875a}## To make the default state storage persist every state
> change, set this to true{color}
> {color:#00875a}## this comes at a performance penalty, but makes sure no
> state is lost even on unclean shutdowns{color}
> {color:#172b4d}nifi.state.management.provider.local.always.persist=true{color}
> {color:#00875a}## To change the frequency at which the default state storage
> is persisted, modify the following{color}
> {color:#172b4d}nifi.state.management.provider.local.auto.persistence.interval=1min{color}
> I think it would be very helpful
> - support state storage for processors (active/inactive)
> - support changing and storing state also for other types of nodes (input
> ports, output ports, funnels, process groups)
> - adding the "enabled" property to the properties of processors in yaml (and
> other types of nodes) by analogy with Apache / nifi,
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
