[
https://issues.apache.org/jira/browse/NIFI-8751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17372811#comment-17372811
]
Mark Bean commented on NIFI-8751:
---------------------------------
What version of NiFi Registry are you running? I believe the Process Group
concurrency settings were added to versioned process groups in NiFi Registry
0.7.0. You may need to upgrade your NiFi Registry.
Sidenote: NiFi Registry source code has now been integrated with the NiFi
codebase. Therefore, these inconsistencies should be minimized by upgrading
NiFi Registry to the same version as NiFi.
> Process Group concurrency configuration does not update when deploying to
> another environment
> ---------------------------------------------------------------------------------------------
>
> Key: NIFI-8751
> URL: https://issues.apache.org/jira/browse/NIFI-8751
> Project: Apache NiFi
> Issue Type: Bug
> Affects Versions: 1.12.1
> Reporter: naveen kumar saharan
> Priority: Major
>
> We have PG, where we have used the Process Group FlowFile Concurrency as
> single flow file per node, the same e are not able to see when checked into
> registry and pulling the PG in another environment.
> the setting gets reset to unbounded.
>
> PG A checked into registry
> PG B is inside PG A.
>
> PG B has flowfile concurrency configuration setting as Single Flowfile per
> node.
>
> Now, when pulling from registry PG B in new environment reset the PG flowfile
> configuration
>
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
