You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "John Wise (Jira)" <ji...@apache.org> on 2023/04/18 18:11:00 UTC

[jira] [Created] (NIFI-11468) Attribute values are converted to sensitive values after NiFi upgrades, when custom nars are used

John Wise created NIFI-11468:
--------------------------------

             Summary: Attribute values are converted to sensitive values after NiFi upgrades, when custom nars are used
                 Key: NIFI-11468
                 URL: https://issues.apache.org/jira/browse/NIFI-11468
             Project: Apache NiFi
          Issue Type: Bug
          Components: Core Framework
            Reporter: John Wise


We've recently started experiencing an issue where the attribute values in ~1/4 to 1/3 of the processors in a given flow are changed from plain text to sensitive values.  Those values are then non-recoverable, and must be manually deleted and re-created.

We narrowed this down to some dependencies on previous NiFi versions in our custom nars.  If I exclude the custom nars until after the upgrade is done & the NiFi service is run for the first time after the upgrade, then the all of the standard NiFi processor upgrade versions as expected.

Once I re-add the custom nars, those with previous NiFi dependencies will convert attribute values from plain text to sensitive values.  This seems to be a bug in the processor version upgrade logic.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)