Michael W Moser created NIFI-14478:
--------------------------------------
Summary: Versioned ProcessGroups sometimes do not sync
Key: NIFI-14478
URL: https://issues.apache.org/jira/browse/NIFI-14478
Project: Apache NiFi
Issue Type: Bug
Components: Flow Versioning
Affects Versions: 2.3.0
Reporter: Michael W Moser
Observed that in some scenarios, a Versioned ProcessGroup reports as in-sync
when in reality there are local changes.
# Import a Process Group from a Registry Client
# Make a configuration change in the PG and see that local changes have been
made
# *Copy* the PG and *Paste* it onto the graph
# Observe that the pasted PG shows that flow version is current
# Wait 30 minutes for PG to synchronize with flow registry, pasted PG still
shows that flow version is current
# Make a different change to pasted PG, flow shows as changed, but the first
change in Step 2 does not show as a local difference
The local in-memory copy of a VersionedProcessGroup is the state of the pasted
ProcessGroup. When a ProcessGroup is synchronized with a FlowRegistry, can we
replace the local in-memory copy of the VersionedProcessGroup with the one from
the FlowRegistry?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
