[jira] [Updated] (NIFI-14478) Versioned ProcessGroups are sometimes not in sync with Flow Registry

["Michael W Moser (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/NIFI-14478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael W Moser updated NIFI-14478:
-----------------------------------
    Summary: Versioned ProcessGroups are sometimes not in sync with Flow Registry  (was: Versioned ProcessGroups sometimes do not sync)

> Versioned ProcessGroups are sometimes not in sync with Flow Registry
> --------------------------------------------------------------------
>
>                 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
>            Priority: Major
>
> 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, see that the flow shows there are local changes, but the first change in Step 2 does not show as a local difference
> When a Process Group is created with the contents of a Versioned ProcessGroup, the local in-memory copy of the Versioned ProcessGroup is the state of the pasted Process Group and might not match what's in the Flow Registry.  When a Process Group is synchronized with a Flow Registry, can we replace the local in-memory copy of the Versioned ProcessGroup with the one from the Flow Registry?



--
This message was sent by Atlassian Jira
(v8.20.10#820010)