You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2025/09/07 01:19:00 UTC
[jira] [Commented] (NIFI-14478) Versioned ProcessGroups are sometimes not in sync with Flow Registry
[ https://issues.apache.org/jira/browse/NIFI-14478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18018612#comment-18018612 ]
ASF subversion and git services commented on NIFI-14478:
--------------------------------------------------------
Commit 51a07427d99a69568605920f06ac7f9d3e229da8 in nifi's branch refs/heads/main from Michael W Moser
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=51a07427d9 ]
NIFI-14478 Fixed Modification Tracking for Pasted Versioned Process Groups (#9894)
- Removed ability for a version controlled Process Group to be compared against anything but the version from the Flow Registry
Signed-off-by: David Handermann <ex...@apache.org>
> 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
> Assignee: Michael W Moser
> Priority: Major
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> 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)