[
https://issues.apache.org/jira/browse/NIFI-5186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16482663#comment-16482663
]
ASF GitHub Bot commented on NIFI-5186:
--------------------------------------
Github user markap14 commented on the issue:
https://github.com/apache/nifi/pull/2722
@joewitt re: the unit test failure, I don't believe that it's actually
related to the previous PR necessarily, but is just a timing issue that
happened to trigger here. We could certainly raise the timeout used - it was
waiting up to 2 seconds for the processor state to become STOPPED in the unit
test. We could certainly raise that to 10 seconds or so. I think the timeout
chosen was fairly arbitrary and increasing it would only increase the amount of
time that the tests takes to complete when needed to. If the state transitions
to STOPPED after 25 milliseconds then that's all that it'll wait.
> 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)
