[
https://issues.apache.org/jira/browse/NIFI-10939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17642764#comment-17642764
]
Nathan Gough commented on NIFI-10939:
-------------------------------------
Refreshing canvas or the browser still shows the outer PG as 'modified' after
the inner PG is committed. Again, not exactly sure what the desired behavior is
but I can only assume we don't want users to have to commit every nested PG if
the most inner one is committed?
To give a concrete example, if I have an outer PG, inner PG, and inner-inner
PG, and commit a change inside the inner-inner PG, I will now see uncommitted
changes to inner PG. I commit the changes for the inner PG, and I'll now see
changes for outer PG that I would have to commit. If this is an unfortunate
fact of how nested versions works right now, I guess that's fine, but perhaps
this is unexpected.
> When a Inner Versioned Flow's version changes, all changes within that group
> are shown
> --------------------------------------------------------------------------------------
>
> Key: NIFI-10939
> URL: https://issues.apache.org/jira/browse/NIFI-10939
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Reporter: Mark Payne
> Assignee: Mark Payne
> Priority: Major
> Fix For: 1.20.0, 1.19.1
>
>
> I created a dataflow and placed it under version control.
> I then placed the outer group under version control.
> I proceeded to update the flow in the 'inner' group and save those changes.
> Now, when I view changes to the outer group, it shows that the version does
> not match, but it also shows every difference between my flow and the
> previous version of the inner flow.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
