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

Josef Zahner updated NIFI-15661:
--------------------------------
    Attachment: image-2026-03-03-10-52-07-920.png

> "Show Local Changes" bug for nested NiFi Registry Flows
> -------------------------------------------------------
>
>                 Key: NIFI-15661
>                 URL: https://issues.apache.org/jira/browse/NIFI-15661
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Flow Versioning
>    Affects Versions: 2.6.0, 2.8.0, 2.7.1, 2.7.2
>            Reporter: Josef Zahner
>            Assignee: Pierre Villard
>            Priority: Major
>              Labels: commit, nifi-registry
>         Attachments: image-2026-03-03-08-02-16-542.png, 
> image-2026-03-03-08-04-19-158.png, image-2026-03-03-08-42-38-326.png, 
> image-2026-03-03-10-44-13-562.png, image-2026-03-03-10-45-00-671.png, 
> image-2026-03-03-10-52-07-920.png
>
>
> For NiFi 2.8.0 there was the fix 
> [NIFI-15366|https://issues.apache.org/jira/projects/NIFI/issues/NIFI-15366?filter=allissues&orderby=created+DESC]
>  regarding nested NiFi Flows (stored in NiFi Registry). The behaviour is 
> better, but there is still a GUI display bug in "Versions" -> "Show Local 
> Changes" if we change something in the child PG... So it's still unusable for 
> us with 1000 of processors within a nested Flow.
> Procedure to reproduce the bug:
>  # Insert processors and PGs on the Canvas
>  ** Create a "PG Parent 2.8.0" with one processor and an additional "PG Child 
> 2.8.0":
> !image-2026-03-03-08-02-16-542.png!
>  ** Insert three processors into "PG Child 2.8.0:
> !image-2026-03-03-08-04-19-158.png!
>  # Commit "PG Child 2.8.0" to NiFi Registry
>  # Commit "PG Parent 2.8.0" to NiFi Registry
>  # Move processor "GenerateFlowFile Child1" on the canvas in "PG Child 2.8.0" 
> and commit it to NiFi Registry
>  # {color:#de350b}On the "PG Parent 2.8.0", check "Show Local Changes", this 
> shows the actual bug. We do see here the new Version of the "PG Child 2.8.0", 
> which is absolutely fine - however, there is as well every single processor 
> from the "PG Child 2.8.0" as well. Not ok, the parent should never track 
> anything from child, except the version number.{color}
> !image-2026-03-03-08-42-38-326.png!
>  



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

Reply via email to