[
https://issues.apache.org/jira/browse/NIFI-10205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17682670#comment-17682670
]
Mark Payne commented on NIFI-10205:
-----------------------------------
I also attempted to replicate this but without any success. I created a flow in
1.12.1, added variables to the root group, then made a Parent group, and a
Child group within that, where I used GenerateFlowFile to reference the created
variables. I then pushed Parent to the registry.
Then, I copied the flow.xml.gz to version 1.16.3 and it came up as expected.
There was no copying of variables to child groups, no newly created variables,
etc. No local differences shown.
Can you provide a set of instructions that we can follow that reproduces the
issue? Or provide a copy of a flow created in 1.12.1 that reproduces the issue
in 1.16?
> Process Group variable added during NIFI upgrade
> -------------------------------------------------
>
> Key: NIFI-10205
> URL: https://issues.apache.org/jira/browse/NIFI-10205
> Project: Apache NiFi
> Issue Type: Bug
> Affects Versions: 1.16.3
> Environment: PROD
> Reporter: naveen kumar saharan
> Assignee: Simon Bence
> Priority: Major
> Fix For: 1.20.0
>
> Attachments: image-2022-07-08-19-56-32-132.png,
> image-2022-07-08-20-04-35-585.png
>
>
> We are upgrading 1.12.1 to 1.16.3, after upgrade we are seeing weird behaviour
> # Random variable is getting added to PG
> # Local changes because of point 1 and also Local changes because of
> BackPressure 1Gb config adding to PG
> # Revert for local changes because of point 1,2 not happening. We have to
> deploy the flow after the commit local changes. Which is causing a dummy
> version in registry.
>
> !image-2022-07-08-19-56-32-132.png!
>
> !image-2022-07-08-20-04-35-585.png!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
