[
https://issues.apache.org/jira/browse/NIFI-6314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16850842#comment-16850842
]
Bryan Bende commented on NIFI-6314:
-----------------------------------
This will require a change in the flow diff code that lives in registry:
https://issues.apache.org/jira/browse/NIFIREG-275
> Nested versioned process groups do not update properly
> ------------------------------------------------------
>
> Key: NIFI-6314
> URL: https://issues.apache.org/jira/browse/NIFI-6314
> Project: Apache NiFi
> Issue Type: Bug
> Affects Versions: 1.9.0, 1.9.1, 1.9.2
> Reporter: Bryan Bende
> Priority: Major
> Labels: SDLC
>
> Steps to reproduce:
> # NiFi#1 Create PGA
> # NiFI#1 Create PGB inside PGA
> # NiFI#1 Create some processors inside PGB
> # NIFI#1 Start version control PGB
> # NIFI#1 Start version control PGA
> # NIFI#2 Import a new PG and select PGA v1 (at this point the same exact
> flow is now in both NiFi's)
> # NIFI#1 Go into PGB and modify the properties of some processors
> # NIFI#1 Commit changes on PGB
> # NIFI#1 Commit changes on PGA
> # NIFI#2 Change version on PGA from v1 to v2 (caused PGB to be updated to v2
> since PGA v2 points to PGB v2)
> At this point PGB in NIFI#2 thinks it has been updated to v2 according to the
> version info in flow.xml.gz, but it the actual changes from v2 have not been
> applied, and it shows local changes that looks like they undid what should be
> the real changes. Choosing to revert the local changes will actually get back
> to the real v2 state.
> You can also reproduce this using a single NiFi and having two instances of
> the same versioned process group described above, or by having a single
> instance of the versioned process group and changing the outer PGA back and
> forth between v2 and v1.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
