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

Pierre Villard updated NIFI-15366:
----------------------------------
    Status: Patch Available  (was: In Progress)

> "Show Local Changes" broken for nested NiFi Registry Flows
> ----------------------------------------------------------
>
>                 Key: NIFI-15366
>                 URL: https://issues.apache.org/jira/browse/NIFI-15366
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Core UI
>    Affects Versions: 2.7.1, 2.7.0
>            Reporter: Josef Zahner
>            Assignee: Pierre Villard
>            Priority: Critical
>              Labels: commit, nifi-registry
>         Attachments: image-2025-12-18-15-16-00-333.png, 
> image-2025-12-18-15-17-02-572.png
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Steps to reproduce:
> We have a parent process group (PG) and child PGs. All PGs (parents and 
> childs) are committed to the NiFi Registry. As soon as you change something 
> on the parent canvas, the Dialog "Version -> Show Local Changes" shows a 
> change for every single child PG canvas element (connection, processor, 
> ports,...), plus of course the correct change from the parent canvas.
> Please check the example screenshot below. Parent PG and child PG was 
> committed to the NiFi Registry - no changes in the canvas yet. Go to the 
> parent canvas and add a processor (in my case DeduplicateRecord). The 
> "Version -> Show Local Changes" Dialog shows a lot of changes, which is 
> clearly wrong as the child elements shouldn't be tracked at all in the parent 
> in this case.
> In production we have thousands of elements within a canvas, with that bug we 
> can't see anymore what has changed as soon as we make a single change on the 
> parent.
> h2. PG Parent
> !image-2025-12-18-15-16-00-333.png|width=1436,height=596!
> h2. PG Child:
> !image-2025-12-18-15-17-02-572.png!
>  



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

Reply via email to