[ 
https://issues.apache.org/jira/browse/NIFI-5279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16504985#comment-16504985
 ] 

ASF GitHub Bot commented on NIFI-5279:
--------------------------------------

Github user markap14 commented on the issue:

    https://github.com/apache/nifi/pull/2770
  
    For those reviewing, the simplest way to verify the fix is to create a 
DebugFlow processor. Set the "CustomValidate Pause Time" property to "70 
millis" and when you apply the update, you should see the component is 
validating (it's possible that validation will complete before the 50 ms 
timeout due to java timing precision - if this happens, just configure 
processor and click "Apply" again). Change the duration to 25 millis and you 
should no longer see the validation occurring. Of course, because of timing 
issues you may see some variance.


> Wait a bit for components to finish validation on updates
> ---------------------------------------------------------
>
>                 Key: NIFI-5279
>                 URL: https://issues.apache.org/jira/browse/NIFI-5279
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Core Framework
>            Reporter: Mark Payne
>            Assignee: Mark Payne
>            Priority: Major
>             Fix For: 1.7.0
>
>
> When a Processor, Reporting Task, or Controller Service is updated, it is now 
> validated asynchronously. This provides a faster response time for the web 
> request but can sometimes result in a component showing a "Validating..." 
> state when the response is received, even though the validation logic would 
> complete very quickly. When we make an update to a component, instead of 
> immediately creating the DTO, which would reflect that the state is 
> "validating..." we should wait up to some amount of time (say 50 
> milliseconds?) for the validation to complete, before we create the response. 
> This way, components whose validation completes quickly still show as Valid 
> or Invalid as soon as the response comes back and only those components that 
> actually take a long time to validate will show as Validating.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to