[jira] [Updated] (NIFI-5222) With validation being performed asynchronously, updating a processor causes validation to occur 3 times instead of once

["Mark Payne (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/NIFI-5222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mark Payne updated NIFI-5222:
-----------------------------
    Fix Version/s: 1.7.0
           Status: Patch Available  (was: Open)

> 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)