Github user joewitt commented on the issue:
https://github.com/apache/nifi/pull/2722
@markap14 @mcgilman in looking at this from a user point of view a couple
thoughts:
When validating things which are slow and things which are fast it appears
fast things can be bottlenecked behind fast things. This makes sense but can
we do better? For instance I have a DebugFlow with a 10 sec validation cycle
and an UpdateAttribute processor. it took 10 secs or more for UpdateAttribute
to come back as valid presumably because it was waiting for the next validation
cycle and then perhaps it had to wait behind the slow DebugFlow proc.
Question: Do we have 1 thread or more than one thread for validation? Or
is it just a task we fire off in the typical timer task thread pool?
Question: Can we force a validation cycle whenever some component is change
or more to the point could we initiate 'that component' which changed to be
validated.
---
