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?
Just for information.
This originally described phenomen is solved in the combination NiFi 1.11.1 and NiFi-Registry 0.5.0.
A versioncontrolled process-group which contains disabled processors isn't marked anymore with containing "uncommitted changes" after restart of NiFi.
Only thing that struck me but isn't a problem:
If I disable a versioncontrolled process-group this doesn't lead to marking the process group as having "uncommited changes". But after restart of NiFi this process group is marked as having "uncommited changes". The option "Show local changes" names the differences as "Processor was disabled" for all components within the process group.Now I can proceed a commit and everything stays fine after restart of NiFi.