<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>question Re: Can I configure NiFi/Registry to *not* track processor state changes? in Support Questions</title>
    <link>https://community.cloudera.com/t5/Support-Questions/Can-I-configure-NiFi-Registry-to-not-track-processor-state/m-p/314156#M225900</link>
    <description>&lt;P&gt;I'm in the same situation upgrading Nifi and noticing that all of my processors are showing changed as a result of their state.&amp;nbsp; Having the ability to disable tracking of processor state changes would make for a more seamless upgrade.&amp;nbsp; As &lt;a href="https://community.cloudera.com/t5/user/viewprofilepage/user-id/84797"&gt;@John_Wise&lt;/a&gt; mentioned, is there anyway to accomplish this through configuration?&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 06 Apr 2021 18:28:48 GMT</pubDate>
    <dc:creator>TimA</dc:creator>
    <dc:date>2021-04-06T18:28:48Z</dc:date>
    <item>
      <title>Can I configure NiFi/Registry to *not* track processor state changes?</title>
      <link>https://community.cloudera.com/t5/Support-Questions/Can-I-configure-NiFi-Registry-to-not-track-processor-state/m-p/310511#M224188</link>
      <description>&lt;P&gt;We run multiple NiFi clusters for dev, test, integration, and failover.&amp;nbsp; After recently upgrading from NiFi 1.0.8 to 1.11.4, we've found that NiFi now registers *all* processor state changes as Registry changes.&amp;nbsp; Since these processors must be in different states between the various clusters, it's become very problematic.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is there any way to configure NiFi and/or the Registry to ignore processor states like it used to?&amp;nbsp; I've looked through the properties files and admin docs for both, and haven't found anything configuration that supports that.&lt;/P&gt;</description>
      <pubDate>Wed, 27 Jan 2021 14:47:51 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/Can-I-configure-NiFi-Registry-to-not-track-processor-state/m-p/310511#M224188</guid>
      <dc:creator>John_Wise</dc:creator>
      <dc:date>2021-01-27T14:47:51Z</dc:date>
    </item>
    <item>
      <title>Re: Can I configure NiFi/Registry to *not* track processor state changes?</title>
      <link>https://community.cloudera.com/t5/Support-Questions/Can-I-configure-NiFi-Registry-to-not-track-processor-state/m-p/310588#M224227</link>
      <description>&lt;P&gt;Changing states via the REST API also results in a processor change being reported.&lt;/P&gt;</description>
      <pubDate>Thu, 28 Jan 2021 16:29:37 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/Can-I-configure-NiFi-Registry-to-not-track-processor-state/m-p/310588#M224227</guid>
      <dc:creator>John_Wise</dc:creator>
      <dc:date>2021-01-28T16:29:37Z</dc:date>
    </item>
    <item>
      <title>Re: Can I configure NiFi/Registry to *not* track processor state changes?</title>
      <link>https://community.cloudera.com/t5/Support-Questions/Can-I-configure-NiFi-Registry-to-not-track-processor-state/m-p/314156#M225900</link>
      <description>&lt;P&gt;I'm in the same situation upgrading Nifi and noticing that all of my processors are showing changed as a result of their state.&amp;nbsp; Having the ability to disable tracking of processor state changes would make for a more seamless upgrade.&amp;nbsp; As &lt;a href="https://community.cloudera.com/t5/user/viewprofilepage/user-id/84797"&gt;@John_Wise&lt;/a&gt; mentioned, is there anyway to accomplish this through configuration?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 06 Apr 2021 18:28:48 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/Can-I-configure-NiFi-Registry-to-not-track-processor-state/m-p/314156#M225900</guid>
      <dc:creator>TimA</dc:creator>
      <dc:date>2021-04-06T18:28:48Z</dc:date>
    </item>
    <item>
      <title>Re: Can I configure NiFi/Registry to *not* track processor state changes?</title>
      <link>https://community.cloudera.com/t5/Support-Questions/Can-I-configure-NiFi-Registry-to-not-track-processor-state/m-p/314308#M225964</link>
      <description>&lt;P&gt;&lt;a href="https://community.cloudera.com/t5/user/viewprofilepage/user-id/84797"&gt;@John_Wise&lt;/a&gt;&amp;nbsp;&lt;a href="https://community.cloudera.com/t5/user/viewprofilepage/user-id/87378"&gt;@TimA&lt;/a&gt;&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Let me make sure I understand exactly what change you are making.&lt;BR /&gt;&lt;BR /&gt;I have Process Groups (PG) that are version controlled in my NiFi Registry.&lt;BR /&gt;I have both a NiFi 1.11.4 and NiFi 1.12.1 clusters setup.&lt;BR /&gt;&lt;BR /&gt;If I import a flow from registry and then modify the state (start, stop, disable, enable) of any processor, my PGs do not change to say local changes exist.&amp;nbsp; &amp;nbsp;The state of a processor does not track as a local change.&lt;BR /&gt;&lt;BR /&gt;I suspect some other local change is being made in addition to state change.&lt;/P&gt;&lt;P&gt;If you right click on the PG and under "Version" from displayed context menu select "show local changes" what are the tracked changes being reported?&lt;BR /&gt;&lt;BR /&gt;Hope this helps,&lt;/P&gt;&lt;P&gt;Matt&lt;/P&gt;</description>
      <pubDate>Thu, 08 Apr 2021 15:51:38 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/Can-I-configure-NiFi-Registry-to-not-track-processor-state/m-p/314308#M225964</guid>
      <dc:creator>MattWho</dc:creator>
      <dc:date>2021-04-08T15:51:38Z</dc:date>
    </item>
    <item>
      <title>Re: Can I configure NiFi/Registry to *not* track processor state changes?</title>
      <link>https://community.cloudera.com/t5/Support-Questions/Can-I-configure-NiFi-Registry-to-not-track-processor-state/m-p/314313#M225967</link>
      <description>&lt;P&gt;&lt;a href="https://community.cloudera.com/t5/user/viewprofilepage/user-id/35454"&gt;@MattWho&lt;/a&gt;&amp;nbsp;- I'm running several NiFi 1.11.4 clusters, all connected to an 0.8.0 Registry.&amp;nbsp; If I check out or update a PG on any cluster, then enable or disable any processor within that PG, the Registry state changes to modified (asterisk).&amp;nbsp; Reverting the processor state, changes the Registry state back to current (green checkmark).&lt;BR /&gt;&lt;BR /&gt;I don't recall if the Registry state changed for all types (stopped, started, enabled, disabled) on NiFi 1.0.8, but on 1.11.4, the modified state only occurs when enabling or disabling a processor, not when starting or stopping it.&lt;/P&gt;</description>
      <pubDate>Thu, 08 Apr 2021 17:03:58 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/Can-I-configure-NiFi-Registry-to-not-track-processor-state/m-p/314313#M225967</guid>
      <dc:creator>John_Wise</dc:creator>
      <dc:date>2021-04-08T17:03:58Z</dc:date>
    </item>
    <item>
      <title>Re: Can I configure NiFi/Registry to *not* track processor state changes?</title>
      <link>https://community.cloudera.com/t5/Support-Questions/Can-I-configure-NiFi-Registry-to-not-track-processor-state/m-p/314491#M226073</link>
      <description>&lt;P&gt;&lt;a href="https://community.cloudera.com/t5/user/viewprofilepage/user-id/25389"&gt;@john&lt;/a&gt;&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;I have a HDF 3.4.1.1 cluster (Based off NiFi 1.11.4) setup and with PGs version controlled and can change processors from started to stopped to disabled without it triggering a local change.&amp;nbsp; However, HDF 3.4.1.1 ships with NiFi-Registry 0.3 and not 0.8.&lt;BR /&gt;&lt;BR /&gt;I have another HDF 3.5.2 cluster (based off NiFi 1.12.1) and ships with NiFi-Registry 0.8.&amp;nbsp; In that cluster, I can also change a processor from start to stop to disabled and it does trigger a local change.&lt;BR /&gt;I see someone filled a Jira about this change in behavior:&lt;BR /&gt;&lt;A href="https://issues.apache.org/jira/browse/NIFI-8160" target="_blank"&gt;https://issues.apache.org/jira/browse/NIFI-8160&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;The tracking of Enabled and Disabled State in NiFi-Registry was added as part of:&lt;BR /&gt;&lt;A href="https://issues.apache.org/jira/browse/NIFI-6025" target="_blank"&gt;https://issues.apache.org/jira/browse/NIFI-6025&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Hope this helps,&lt;BR /&gt;Matt&lt;/P&gt;</description>
      <pubDate>Mon, 12 Apr 2021 13:29:19 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/Can-I-configure-NiFi-Registry-to-not-track-processor-state/m-p/314491#M226073</guid>
      <dc:creator>MattWho</dc:creator>
      <dc:date>2021-04-12T13:29:19Z</dc:date>
    </item>
    <item>
      <title>Re: Can I configure NiFi/Registry to *not* track processor state changes?</title>
      <link>https://community.cloudera.com/t5/Support-Questions/Can-I-configure-NiFi-Registry-to-not-track-processor-state/m-p/314513#M226082</link>
      <description>&lt;P&gt;Thanks for the pointer&amp;nbsp;&lt;a href="https://community.cloudera.com/t5/user/viewprofilepage/user-id/35454"&gt;@MattWho&lt;/a&gt;.&amp;nbsp; I've added a comment to NIFI-8160.&lt;/P&gt;</description>
      <pubDate>Mon, 12 Apr 2021 18:34:48 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/Can-I-configure-NiFi-Registry-to-not-track-processor-state/m-p/314513#M226082</guid>
      <dc:creator>John_Wise</dc:creator>
      <dc:date>2021-04-12T18:34:48Z</dc:date>
    </item>
  </channel>
</rss>

