[
https://issues.apache.org/jira/browse/NIFI-10205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17682631#comment-17682631
]
Simon Bence commented on NIFI-10205:
------------------------------------
Hi Naveen! I tried to reproduce this the following way:
- Creating a simple flow using NiFi 1.12.1
- I added the flow under version control into a registry
- Using NiFi 1.16.3 I added the flow to the canvas from the registry
To enforce possible differences in backpressure value, I also tried this with
changing the default backpressure value in 1.12.1. My experience as smooth and
the flow was added without local changes. In order to narrow the possible
reasons, please let me ask some questions:
- It is not clear to me that the changes in the backpressure (2) were
intentional and made by hand or this is unintentional? (Have you happened to
change the NiFi's backpressure properties?)
- Do you use any S3 related processor might need custom properties? Or is it
possible that the flow contains custom processors? (Atlas reporting uses
strings like "aws_s3_bucket" but I found no reference for "aws_s3_bucket_ops")
- If it would be possible to share a flow.xml or template which falls under the
circumstances of the issue, that would be a great help to find the cause for
this behaviour
(Note: DEFAULT_BACKPRESSURE_DATA_SIZE_CHANGED is an existing thing, but this
way I did not manage to achieve)
> 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)
