I have a custom processor actively used in customer flows. I need to
enhance it, but avoid invalidating it when I update custom's existing
NiFi installations.
I know that the processor properties, in particular, the conflict
between the property .name()and .displayName(), is a good way to
I understand you can have multiple versions of a processor loaded at once
(from separate NARs).
Existing flows should continue to use the already configured version, then
you can right-click the processor in the UI and change its version when
you're ready and fix any issues at that time. This shou
I will be very happy to read what others contribute. Chris' suggestion,
which has huge implications, I think, for my IDE and project structure,
will be something to look into.
However, I was hoping someone would articulate the difference between
*property names* and *property display names*, w
Russ,
You can change the property descriptors display name without a problem. You
should *not* change the name of the property. If a property exists with no
display name specified, you can introduce a display name. This just dictates
what the UI will call it. So that can be changed to improve
