[
https://issues.apache.org/jira/browse/NIFI-11570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17799187#comment-17799187
]
Bryan Bende commented on NIFI-11570:
------------------------------------
I think using the propertyDescriptors would be a way to solve it, but I think
we purposely don't populate them in the flow.json because it would drastically
increase the size of the file and most of it would be repetitive, meaning if
there are 10 instances of ProcessorX and it has no dynamic properties, then all
10 of those processors will write out the same propertyDescriptors in flow.json.
> Processors have difficulty restoring dynamic properties when leaving ghost
> mode
> -------------------------------------------------------------------------------
>
> Key: NIFI-11570
> URL: https://issues.apache.org/jira/browse/NIFI-11570
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 1.19.1
> Reporter: Nissim Shiman
> Assignee: Nissim Shiman
> Priority: Major
>
> When a processor with non sensitive dynamic properties is started in ghost
> mode due to its underlying nar being missing, it will have a difficult time
> being restored even when its nar has been replaced.
> The dynamic properties will be identified as being sensitive and not able to
> be accessed.
> So for example, if a dynamic property added to GenerateFlowFile and
> nifi-standard-nar is removed from lib and nifi is restarted, GenerateFlowFile
> will come up in ghosted mode (as expected).
> When nifi-standard-nar is replaced and nifi is restarted, GenerateFlowFile
> will be restored, but its dynamic property will not be accessable.
> This was originally filed as a second part of NIFI-11109, but after looking
> more into the underlying causes/symptoms, realized that these are two
> different issues.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
