[
https://issues.apache.org/jira/browse/NIFI-1464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15169201#comment-15169201
]
ASF GitHub Bot commented on NIFI-1464:
--------------------------------------
Github user markap14 commented on the pull request:
https://github.com/apache/nifi/pull/210#issuecomment-189326513
In StandardFlowSerializer, Line 314, we write out the Processor's Scheduled
State. This is done so that when we restore the flow on restart, we know what
state the Processor is in. So if we are adding new states to Scheduled State,
we need to be sure to account for that there. Specifically, I think we should
just update StandardFlowSerializer to write out a state of RUNNING if the state
is STARTING and a state of STOPPED if it's STOPPING. Then we don't have to
worry about the code that restores the state because what is written to the
flow.xml is the state that we want to use when we restore the flow.
> Refactor lifecycle code for Processors and other components
> -----------------------------------------------------------
>
> Key: NIFI-1464
> URL: https://issues.apache.org/jira/browse/NIFI-1464
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Oleg Zhurakousky
> Assignee: Oleg Zhurakousky
> Fix For: 0.6.0
>
>
> Similar lifecycle handling improvements that went in as part of the NIFI-1164
> for ControllerServices, could/should be applied to other components (e..g,
> Processors).
> The improvements may also help to address NIFI-78 (may be without killing the
> thread).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
