[
https://issues.apache.org/jira/browse/NIFI-10939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17643094#comment-17643094
]
Joe Witt commented on NIFI-10939:
---------------------------------
Once you commit that inner process group you now have the inner process group
at the next version which is different than the version the parent PG was
pointing at. Thus the parent needs to be committed as well to reflect this
change if that is also desired. You have to keep in mind someone else might
also be using that versioned parent process group on their flow and this
mechanism needs to make all of that able to be in sync. This is an important
part of this fairly complex nested versioned group mechanism.
> 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)
