<?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 Custom Python Processor Problems After NiFi Upgrade from 2.0.0-M2 in Support Questions</title>
    <link>https://community.cloudera.com/t5/Support-Questions/Custom-Python-Processor-Problems-After-NiFi-Upgrade-from-2-0/m-p/407796#M252637</link>
    <description>&lt;DIV&gt;Hi,&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;We've developed custom Python-based processors (GetCheckpoint, UpdateCheckpoint) for NiFi 2.0.0-M2 to handle checkpoint creation and updates and put it in&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;python/extensions/GetCheckpoint.py&lt;/DIV&gt;&lt;DIV&gt;python/extensions/UpdateCheckpoint.py&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;These processors worked correctly in 2.0.0-M2. However, after upgrading to NiFi 2.1.0, we’re encountering the following issues:&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp; &amp;nbsp; All custom processor properties now display the message:&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp; &amp;nbsp; “Sensitive of the parameter does not match the sensitivity of the property”&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp; &amp;nbsp; — even though the properties were not marked as sensitive in the code.&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp; &amp;nbsp; When adding a new instance of the processor, properties appear correct, but state handling breaks.&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp; &amp;nbsp; We modified and rebuilt the processors and, when adding them freshly to a flow, they seem to work correctly without any errros. However, existing GetCheckpoint /UpdateCheckpoint still show the sensitivity mismatch warning.&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp; &amp;nbsp; Even for newly created flows, if we simply change the processor version (&amp;nbsp; &amp;nbsp; class ProcessorDetails:&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; version = '2.3.0' to&amp;nbsp; &amp;nbsp; &amp;nbsp;class ProcessorDetails:&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; version = '2.4.0'),&lt;BR /&gt;&lt;BR /&gt;the same sensitivity error returns.&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;Questions:&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp; &amp;nbsp; What is the correct process for upgrading or modifying custom Python processors ?&lt;BR /&gt;&amp;nbsp; &amp;nbsp; What is the correct way to Upgrade NiFI with custom processrs in place?&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp; &amp;nbsp; Is there a way to avoid manually replacing every instance of the processor across all existing flows?&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;Any insight or recommendations would be appreciated.&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;Thanks!&lt;/DIV&gt;</description>
    <pubDate>Fri, 02 May 2025 12:11:27 GMT</pubDate>
    <dc:creator>Mandear</dc:creator>
    <dc:date>2025-05-02T12:11:27Z</dc:date>
    <item>
      <title>Custom Python Processor Problems After NiFi Upgrade from 2.0.0-M2</title>
      <link>https://community.cloudera.com/t5/Support-Questions/Custom-Python-Processor-Problems-After-NiFi-Upgrade-from-2-0/m-p/407796#M252637</link>
      <description>&lt;DIV&gt;Hi,&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;We've developed custom Python-based processors (GetCheckpoint, UpdateCheckpoint) for NiFi 2.0.0-M2 to handle checkpoint creation and updates and put it in&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;python/extensions/GetCheckpoint.py&lt;/DIV&gt;&lt;DIV&gt;python/extensions/UpdateCheckpoint.py&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;These processors worked correctly in 2.0.0-M2. However, after upgrading to NiFi 2.1.0, we’re encountering the following issues:&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp; &amp;nbsp; All custom processor properties now display the message:&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp; &amp;nbsp; “Sensitive of the parameter does not match the sensitivity of the property”&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp; &amp;nbsp; — even though the properties were not marked as sensitive in the code.&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp; &amp;nbsp; When adding a new instance of the processor, properties appear correct, but state handling breaks.&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp; &amp;nbsp; We modified and rebuilt the processors and, when adding them freshly to a flow, they seem to work correctly without any errros. However, existing GetCheckpoint /UpdateCheckpoint still show the sensitivity mismatch warning.&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp; &amp;nbsp; Even for newly created flows, if we simply change the processor version (&amp;nbsp; &amp;nbsp; class ProcessorDetails:&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; version = '2.3.0' to&amp;nbsp; &amp;nbsp; &amp;nbsp;class ProcessorDetails:&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; version = '2.4.0'),&lt;BR /&gt;&lt;BR /&gt;the same sensitivity error returns.&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;Questions:&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp; &amp;nbsp; What is the correct process for upgrading or modifying custom Python processors ?&lt;BR /&gt;&amp;nbsp; &amp;nbsp; What is the correct way to Upgrade NiFI with custom processrs in place?&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp; &amp;nbsp; Is there a way to avoid manually replacing every instance of the processor across all existing flows?&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;Any insight or recommendations would be appreciated.&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;Thanks!&lt;/DIV&gt;</description>
      <pubDate>Fri, 02 May 2025 12:11:27 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/Custom-Python-Processor-Problems-After-NiFi-Upgrade-from-2-0/m-p/407796#M252637</guid>
      <dc:creator>Mandear</dc:creator>
      <dc:date>2025-05-02T12:11:27Z</dc:date>
    </item>
    <item>
      <title>Re: Custom Python Processor Problems After NiFi Upgrade from 2.0.0-M2</title>
      <link>https://community.cloudera.com/t5/Support-Questions/Custom-Python-Processor-Problems-After-NiFi-Upgrade-from-2-0/m-p/408030#M252650</link>
      <description>&lt;P&gt;&lt;a href="https://community.cloudera.com/t5/user/viewprofilepage/user-id/124987"&gt;@Mandear&lt;/a&gt;&amp;nbsp;Welcome to the Cloudera Community!&lt;BR /&gt;&lt;BR /&gt;To help you get the best possible solution, I have tagged our NiFi experts&amp;nbsp;&lt;a href="https://community.cloudera.com/t5/user/viewprofilepage/user-id/35454"&gt;@MattWho&lt;/a&gt;&amp;nbsp;&lt;a href="https://community.cloudera.com/t5/user/viewprofilepage/user-id/105558"&gt;@joseomjr&lt;/a&gt;&amp;nbsp; who may be able to assist you further.&lt;BR /&gt;&lt;BR /&gt;Please keep us updated on your post, and we hope you find a satisfactory solution to your query.&lt;/P&gt;</description>
      <pubDate>Tue, 06 May 2025 07:04:02 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/Custom-Python-Processor-Problems-After-NiFi-Upgrade-from-2-0/m-p/408030#M252650</guid>
      <dc:creator>DianaTorres</dc:creator>
      <dc:date>2025-05-06T07:04:02Z</dc:date>
    </item>
  </channel>
</rss>

