[
https://issues.apache.org/jira/browse/NIFI-8160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17951436#comment-17951436
]
Jordan Sammut commented on NIFI-8160:
-------------------------------------
Thanks for the info [~bbende] , I will investigate why I'm seeing this
behaviour on my end.
My primary concern with the current approach is for processes such a
ConsumeKafka, where we have more environments on prod, than on stage for
example. The only option is to have the ones which aren't needed stopped, but
this can create problems with bulk actions such as a start/stop all as you
would be affecting the unwanted consumers on that particular environment.
I do however understand that the current behaviour is useful for other use
cases, which is why it would be best if this was something configurable at PG
level or system wide
> Enable / Disable should not be seen as a change in Nifi registry
> ----------------------------------------------------------------
>
> Key: NIFI-8160
> URL: https://issues.apache.org/jira/browse/NIFI-8160
> Project: Apache NiFi
> Issue Type: Bug
> Affects Versions: 2.4.0
> Reporter: DEOM Damien
> Priority: Critical
>
> Enable / Disable should not be seen as a change in Nifi registry.
> It interferes with the release management when we use several clusters (
> integration / production )
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
