[
https://issues.apache.org/jira/browse/NIFI-10205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17682160#comment-17682160
]
John Wise commented on NIFI-10205:
----------------------------------
We noticed this as well on some of our clusters which utilize *optional*
variables in some of the flows to differentiate between those servers which
need to connect via a proxy service and those which don't. Our variables are
defined on the root canvas so that they can be used globally *without* having
to specify a parameter context (which is why we still don't use those). After
our most recent upgrade to 1.17.0, the variable is now being "pulled into" all
process groups below the root level canvas, which gets flagged as a Registry
change. This is not the ideal behavior; if someone asked for it, then it
should be an option when configuring either NiFi or the Registry, much as the
state of processors and ports should an optional configuration when saving a
process group to the Registry.
Both of those changes (variables & processor/port states) have caused numerous
problems maintaining flows across our dev, staging, pre-prod & production
environments, because nothing's optional now.
> 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
> Priority: Major
> 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)
