Andy LoPresto created NIFI-5183:
-----------------------------------
Summary: Automatically refresh (local) canvas on component state
change
Key: NIFI-5183
URL: https://issues.apache.org/jira/browse/NIFI-5183
Project: Apache NiFi
Issue Type: Improvement
Components: Core UI
Affects Versions: 1.6.0
Reporter: Andy LoPresto
This may be captured in [~andrewmlim]'s UI/UX notes, but I propose that when a
component state is changed (i.e. started/stopped), the (local) canvas is
refreshed automatically. Basically, when new users start a processor, because
the canvas doesn't refresh immediately, they do not always get immediate
feedback and realize it is processing flowfiles.
I also understand that on canvases with giant flows, it is not always
performant to refresh the entire canvas on every change. Perhaps just the local
process group or N processors, or just upstream/downstream connections could be
refreshed immediately, with other components being refreshed from the scheduled
refresh action.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
