[
https://issues.apache.org/jira/browse/NIFI-8751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
naveen kumar saharan updated NIFI-8751:
---------------------------------------
Description:
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
was:
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.
> 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)
