The flow.xml.gz/flow.json.gz has the (now removed) properties as part of the definition. Therefore, they still appear on the updated processor, but now as dynamic properties. The only recourse is to remove the properties from existing processor instances, or to delete the processor and instantiate a new one.
One way we deal with this situation is to deprecate the property, but keep it as part of the processor definition. It has no functional value, and the documentation indicates that it is deprecated. This gives users a period of time to adjust their flows. Eventually, when a new major release version of the custom NAR is released, the deprecated properties can be removed completely. -Mark On Thu, Jul 20, 2023 at 7:43 PM Russell Bateman <r...@windofkeltia.com> wrote: > I have a custom processor I modified losing a few properties because a > specification change made them useless. I removed them. The processor > works, but in configuration for this processor (in the NiFi UI), the > processor appears to have kept them, i.e.: they're not disappearing. I > would have expected trash cans on each, but they're just still there. > > Yes, the processor bears the latest NAR version number and there is no > "duplicate" or older NAR in the /extensions/ subdirectory. > > Is my best recourse to remove the processor from the flow and re-add it? > This is not a problem, but I'll have down-streamers with their own flows > I'm not in contact with who will find this behavior unsettling. I could > issue documentation, but I try to keep extra work to a minimum for them. > > Thanks for any thoughts. > > Russ
