[
https://issues.apache.org/jira/browse/NIFI-5186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Gilman updated NIFI-5186:
------------------------------
Description: This Jira is a follow up to NIFI-950. The new asynchronous
validation introduces a new state VALIDATING. This VALIDATING state will be
entered following any modifications (create, update) to the component
(Processor, Controller Service, Reporting Task). All component validation is
done in the background on a recurring interval. When obtaining the current
state, we will return the last known state unless it is VALIDATING as a result
of a modification. (was: This Jira is a follow up to NIFI-950. The new
asynchronous validation introduces a new state VALIDATING. This VALIDATING
state will be shown following any modifications (create, update) to the
component (Processor, Controller Service, Reporting Task). All component
validation is done in the background on a recurring interval or following a
modification. When obtaining the current state, we will return the last known
state unless we are returning it as part of a modification (in which case we
return VALIDATING). )
> Update UI to account for asynchronous validation
> ------------------------------------------------
>
> Key: NIFI-5186
> URL: https://issues.apache.org/jira/browse/NIFI-5186
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core UI
> Reporter: Matt Gilman
> Assignee: Matt Gilman
> Priority: Blocker
> Fix For: 1.7.0
>
>
> This Jira is a follow up to NIFI-950. The new asynchronous validation
> introduces a new state VALIDATING. This VALIDATING state will be entered
> following any modifications (create, update) to the component (Processor,
> Controller Service, Reporting Task). All component validation is done in the
> background on a recurring interval. When obtaining the current state, we will
> return the last known state unless it is VALIDATING as a result of a
> modification.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
