[
https://issues.apache.org/jira/browse/NIFI-7623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hsin-Ying Lee updated NIFI-7623:
--------------------------------
Description:
When using the registry to revert or change the version of the flow, sometimes
the changes only were position, color style, and connection bend points
changes, it's not required to stop the upstream/downstream processor.
When the processor was doing the long-term tasks, the version control would not
complete until the processors stopped, even changes do not require the
processor stopped.
was:
We tried to use the registry to change version/revert for a versioned PG, the
changes only were processor position, color style, and connection bend points
changes.
When the processor was doing the long time tasks, the version control would not
complete until the processors stopped, even that is not necessary to stop.
If we tried to cancel the request, we also have to wait for the processors to
stop and go back to start it manually.
I'm trying to fix this issue, and make a PR for this.
> Reduce unnecessary processors restart when using registry to update the flow
> ----------------------------------------------------------------------------
>
> Key: NIFI-7623
> URL: https://issues.apache.org/jira/browse/NIFI-7623
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework, Flow Versioning
> Reporter: Hsin-Ying Lee
> Priority: Major
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> When using the registry to revert or change the version of the flow,
> sometimes the changes only were position, color style, and connection bend
> points changes, it's not required to stop the upstream/downstream processor.
> When the processor was doing the long-term tasks, the version control would
> not complete until the processors stopped, even changes do not require the
> processor stopped.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
