[
https://issues.apache.org/jira/browse/NIFI-1119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Gilman reopened NIFI-1119:
-------------------------------
This patch has introduced a race condition that may cause the revision to be
checked before the flow has loaded. When this happens, the revision check will
fail and the user will be shown the message indicating that someone else has
modified the flow.
> 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.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)
