Github user scottyaslan commented on the issue:
https://github.com/apache/nifi/pull/2722
Thanks @mcgilman this has been merged to master.
---
Github user joewitt commented on the issue:
https://github.com/apache/nifi/pull/2722
@markap14 understood and agree. I'm +1 on this. Will also look at
NIFI-5222 as well now
---
Github user markap14 commented on the issue:
https://github.com/apache/nifi/pull/2722
@joewitt I think I understand now what you were seeing. If I create two
different DebugFlow processors, each with a validation pause of 10 seconds, and
then I create an UpdateAttribute and configure
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
Github user markap14 commented on the issue:
https://github.com/apache/nifi/pull/2722
@joewitt your observations are very interesting - i am not seeing that at
all. I created a DebugFlow with a validation pause of 10 seconds. Then I
created an update attribute. UpdateAttribute was
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
Github user joewitt commented on the issue:
https://github.com/apache/nifi/pull/2722
@mcgilman @markap14 this test finding is related to Mark's preceding PR for
this most likely but
`[ERROR] Tests run: 15, Failures: 1, Errors: 0, Skipped: 2, Time elapsed:
16.555 s <<<
