[
https://issues.apache.org/jira/browse/NIFI-5186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16482524#comment-16482524
]
ASF GitHub Bot commented on NIFI-5186:
--------------------------------------
Github user markap14 commented on the issue:
https://github.com/apache/nifi/pull/2722
@joewitt your observations are very interesting - i am not seeing that at
all. I created a DebugFlow with a validation pause of 10 seconds. Then I
created an update attribute. UpdateAttribute was immediately invalid. I
triggering validation to occur on DebugFlow and then UpdateAttribute and saw
instance responses for UpdateAttribute's validation.
So to answer your questions specifically:
1) We use a thread pool with 5 threads.
2) Any time a component changes (specifically, if a property is set,
annotation data is set, incoming connections or outgoing connections are set)
then we initiate validation for the component.
Of note, when you get back the "Validating" icon, that icon will not go
away until the status is refreshed, which happens by default every 30 seconds.
If you right-click on the canvas and refresh, that will also refresh it. Just
wanted to make sure that you did refresh the canvas in that time interval?
> 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)
