[
https://issues.apache.org/jira/browse/NIFI-5186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16481191#comment-16481191
]
ASF GitHub Bot commented on NIFI-5186:
--------------------------------------
Github user joewitt commented on the issue:
https://github.com/apache/nifi/pull/2722
@markap14 @mcgilman in looking at this from a user point of view a couple
thoughts:
When validating things which are slow and things which are fast it appears
fast things can be bottlenecked behind fast things. This makes sense but can
we do better? For instance I have a DebugFlow with a 10 sec validation cycle
and an UpdateAttribute processor. it took 10 secs or more for UpdateAttribute
to come back as valid presumably because it was waiting for the next validation
cycle and then perhaps it had to wait behind the slow DebugFlow proc.
Question: Do we have 1 thread or more than one thread for validation? Or
is it just a task we fire off in the typical timer task thread pool?
Question: Can we force a validation cycle whenever some component is change
or more to the point could we initiate 'that component' which changed to be
validated.
> 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)
