[
https://issues.apache.org/jira/browse/NIFI-7381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17088228#comment-17088228
]
Otto Fowler commented on NIFI-7381:
-----------------------------------
I believe this is fixed by https://github.com/apache/nifi/pull/4201
> Wait Processor Not Waiting When Used Twice for Same Flow File
> -------------------------------------------------------------
>
> Key: NIFI-7381
> URL: https://issues.apache.org/jira/browse/NIFI-7381
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 1.11.3, 1.11.4
> Reporter: Jim
> Priority: Major
>
> When a flow file is routed to a Wait processor, the processor adds an
> attribute with the current timestamp called "wait.start.timestamp" which it
> uses to compare against the Expiration Duration to determine when to send the
> flow file to the "expired" relationship.
> If that flow file is presented a second time to the same Wait processor, the
> processor is not updating the "wait.start.timestamp" and is therefore
> immediately expiring the flow file. As a workaround, I inserted and
> UpdateAttribute processor to delete the attribute before it goes to the Wait
> processor. Now it behaves as expected.
> Though not tested, the flow file may also immediately expire if it was routed
> to a different Wait processor, since the attribute with the current timestamp
> is the same for all Wait processors.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
