[
https://issues.apache.org/jira/browse/NIFI-11001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Witt updated NIFI-11001:
----------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Incorrect Local Changes shown when upgrading from 1.18.0 to 1.19.1
> ------------------------------------------------------------------
>
> Key: NIFI-11001
> URL: https://issues.apache.org/jira/browse/NIFI-11001
> Project: Apache NiFi
> Issue Type: Bug
> Affects Versions: 1.19.1
> Reporter: Bryan Bende
> Assignee: Mark Payne
> Priority: Major
> Fix For: 1.20.0
>
> Attachments: Parent-from-1.18.0.json, Screen Shot 2022-12-21 at
> 4.27.47 PM.png
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Scenario to reproduce...
> Using 1.18.0, do the following:
> * Create a PG named Parent
> * Inside Parent, create a PG named Child
> * Inside Child add GenerateFlowFile connected to UpdateAttribute
> * Start version control on Parent
> * Export Child without services
> * Import the exported Child inside Parent, so there are two Child PGs
> * Commit changes
> * Export Parent without services
> At this point if you restart 1.18.0 nifi, it comes back up fine showing
> Parent as up to date.
> Now go to 1.19.1 NiFi:
> * Import Parent flow definition
> * Start version control
> * Restart NiFi
> At this point, NiFi comes back up and says there are local changes to commit,
> even though there weren't before restart. See attached screenshot.
> On a similar note, if you try to perform the initial steps using latest NiFi,
> you get an error trying to import the exported Child PG, and the error says
> one of the components for the connection can't be located. So this seems like
> a related issue involving something that changed with versioned component ids.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
