[ https://issues.apache.org/jira/browse/NIFI-8160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17319646#comment-17319646 ]
John Wise commented on NIFI-8160: --------------------------------- Contrary to the requestor's needs resolved in [NIFI-6025] Track Enabled/Disabled State in Registry - ASF JIRA (apache.org), we *don't* want to track enabled/disabled processor changes in the Registry. Most of our CMed flows are utilized across different clusters used for dev, test/integration, staging, failover, and production environments. Given the different types and volumes of data we're processing, and the need to manually changeover some flows, we utilize enable/disable extensively. Please consider making enable/disable detection an OPTION in nifi-registry.properties. At the moment, it's causing us no end of issues with people mistakenly checking in "changed" groups, which then get updated on other clusters and break the dataflows on those. > 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 > Reporter: DEOM Damien > Priority: Major > > 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.3.4#803005)