Github user jtstorck commented on the issue:
https://github.com/apache/nifi/pull/2219
The NiFi Registry integration looks great! I did noticed a syncing/timing
issue when working with two process groups referencing the same versioned flow.
If one of these process groups is modified (for example, a processor was
added) and the changes are committed, the second process group will report that
it's up to do date, though it doesn't have any of the changes that were
committed. It appears there's a period of time between the commit of the
changes and NiFi's retrieval/integration of the updates from the registry.
Refreshing the NiFi UI during this time period will still show both process
groups as up to date, though the process group with the second instance of that
versioned flow will still not have the changes. Some moments later, the second
process group's icon will report that there's a new version. Updating that
second process group to the new version works as expected.
I can see this only being an issue on the node used to make these changes,
and will really only be observed when there's another process group with the
same flow elsewhere on the canvas. It does seem a bit odd that, on that
particular node, the second process group of the versioned flow does not
immediately show that a new version is available.
---
