Custom Python Processor Problems After NiFi Upgrade from 2.0.0-M2

[#1]

Hi,

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 

python/extensions/GetCheckpoint.py

python/extensions/UpdateCheckpoint.py

These processors worked correctly in 2.0.0-M2. However, after upgrading to NiFi 2.1.0, we’re encountering the following issues:

    All custom processor properties now display the message:

    “Sensitive of the parameter does not match the sensitivity of the property”

    — even though the properties were not marked as sensitive in the code.

    When adding a new instance of the processor, properties appear correct, but state handling breaks.

    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.

    Even for newly created flows, if we simply change the processor version (    class ProcessorDetails:

        version = '2.3.0' to     class ProcessorDetails:

        version = '2.4.0'),

the same sensitivity error returns.

Questions:

    What is the correct process for upgrading or modifying custom Python processors ?
    What is the correct way to Upgrade NiFI with custom processrs in place?

    Is there a way to avoid manually replacing every instance of the processor across all existing flows?

Any insight or recommendations would be appreciated.

Thanks!

[#2]

@Mandear Welcome to the Cloudera Community!

To help you get the best possible solution, I have tagged our NiFi experts @MattWho @joseomjr  who may be able to assist you further.

Please keep us updated on your post, and we hope you find a satisfactory solution to your query.