[
https://issues.apache.org/jira/browse/NIFI-1119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15058184#comment-15058184
]
Joseph Percivall commented on NIFI-1119:
----------------------------------------
Ran an install contrib check, tried many different ways of getting into the web
app (clean browser, browser that had been opened before but shut nifi down,
multiple tabs, etc.) and did them with Safari, Firefox and Chrome. I didn't see
the race condition once. Checked out the code and verified it made sense.
+1
When I originally saw the "race" condition before I thought it was due to there
being remnants of flows in my cache.
> Right-click -> Refresh must also refresh the flow revision
> ----------------------------------------------------------
>
> Key: NIFI-1119
> URL: https://issues.apache.org/jira/browse/NIFI-1119
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core UI
> Affects Versions: 0.3.0
> Reporter: Andrew Grande
> Assignee: Matt Gilman
> Priority: Minor
> Labels: easyfix
> Fix For: 0.5.0
>
> Attachments: 0001-NIFI-1119-2.patch, 0001-NIFI-1119.patch
>
>
> Following up on a discussion with [~mcgilman]. When updating the flow via a
> REST api from an external process, there is a period of time where user
> doesn't see flow updates. There is no way for the user to 'refresh' either,
> has to wait for the next 30s cycle (default). From a UX standpoint, the
> Refresh should update to the latest state of everything (stats and flow).
> Suggestion: have the context menu's _Refresh status_ action fire an
> additional request to the *revision* API to detect external changes. The UI
> will flag the view as out of sync (maybe it should just update, because a
> user is already trying to force an update?)
> In light of this change, it makes sense to rename the action to a simple
> Refresh (drop the ' status' part).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
