Details
-
Improvement
-
Status: Open
-
Minor
-
Resolution: Unresolved
-
None
-
None
-
None
Description
Some of our team members have complained that process groups updated via NiFi Registry don’t maintain the Flow Configuration History from the node/cluster where a given set of changes were made. They want it primarily to figure out who made changes, more so than what actually changed.
I presume that not storing that information in the Registry is by design, since the history is local to the node on which the changes were made.
I’ve shown them how to use the API to perform diffs, but that’s not acceptable to them in its current form either.