You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@nifi.apache.org by "Bryan Bende (Jira)" <ji...@apache.org> on 2022/12/21 21:32:00 UTC

[jira] [Commented] (NIFI-11001) Incorrect Local Changes shown when upgrading from 1.18.0 to 1.19.1

    [ https://issues.apache.org/jira/browse/NIFI-11001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17651004#comment-17651004 ] 

Bryan Bende commented on NIFI-11001:
------------------------------------

Might be related to NIFI-10985, but it is unclear.

> 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
>            Priority: Major
>         Attachments: Parent-from-1.18.0.json, Screen Shot 2022-12-21 at 4.27.47 PM.png
>
>
> 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)