there are process groups in my NiFi (1.10.0) which contain disabled processors.
These process groups are versioned and all changes are committed.
As soon as the NiFi instance is restarted these process groups are marked as changed and "show local changes" here:
I would like to know if this behaviour of NiFi is "normal". So far I have not noticed this fact.
It is misleading when uncommitted changes are shown and it is not possible to avoid that disabled processors are included.
Does anyone know the phenomenon described above?
Is there a solution for it?
Thanks for any advice.
refering to nifi-registry-bootstrap.log we use v0.3.0
But I'm pretty sure that I didn't watch this behaviour before using NiFi 1.10.0 (former version 1.9.2).
Can you confirm this connection with the NiFi version?
That bug was actually introduced through a change that went in to NiFi 1.8 that pushed included the enabled/disabled state to registry. But NiFi registry shipping at that time had not yet been updated to store this new parameter.
Do you still see the issue even after upgrading to NiFi-Registry 0.5?