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 should allow you to manage the roll-out per flow when appropriate. The extensions/ directory can be used to auto load new NARs into a running instance (but removing a NAR doesn't auto unload it). Adding anything to the lib/ directory will require a restart. Once all flows are updated, the old version NAR can be removed and nifi restarted to unload the resources. Cheers, Chris Sampson On Wed, 30 Dec 2020, 18:23 Russell Bateman, <[email protected]> wrote: > 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 get > myself into trouble by changing the wording, correcting spelling, etc. > > Also, adding to or subtracting properties and/or relationships is a > good way to blow it all up. > > How does versioning the processor solve any of this? > > Etc. > > Can anyone share canonical advice on this? > > Thanks, > Russ >
