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

ASF subversion and git services commented on NIFI-5222:
-------------------------------------------------------

Commit eb0b4283e800636b8722fadfebce34e3df094196 in nifi's branch 
refs/heads/master from [~markap14]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=eb0b428 ]

NIFI-5222: Prevent validating components multiple times for each update
- Avoid triggering async validation for each update to component when 
instantiating a template (such as copy/paste or templates). Added debug logging 
to indicate when and why we are triggering validation; removed unit test that 
made poor assumptions about the inner workings of the FlowSynchronizer that 
resulted in failures when we make calls into processors that the unit test 
doesn't know about"

This closes #2731.


> With validation being performed asynchronously, updating a processor causes 
> validation to occur 3 times instead of once
> -----------------------------------------------------------------------------------------------------------------------
>
>                 Key: NIFI-5222
>                 URL: https://issues.apache.org/jira/browse/NIFI-5222
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Core Framework
>    Affects Versions: 1.7.0
>            Reporter: Mark Payne
>            Assignee: Mark Payne
>            Priority: Major
>             Fix For: 1.7.0
>
>
> With the merge of NIFI-950, we now have processors, controller services, and 
> reporting tasks being validated asynchronously. Each time that properties, 
> annotation data, or auto-terminated relationships are set, a task is kicked 
> off in the background to perform validation. Additionally, if any connections 
> are added/removed, it kicks off the task.
> Right now, though, if a user clicks to configure a processor and then clicks 
> Apply, what happens on the back end is that we call setProperties(), 
> setAnnotationData(), and setAutoTerminatedRelationships() in the request. As 
> a result, we kick off validation 3 times. Instead, we should avoid kicking 
> off that background task until we've completed all updates to the 
> processor/controller service/reporting task. Then trigger validation only 
> once.



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

Reply via email to