[
https://issues.apache.org/jira/browse/NIFI-5892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16726812#comment-16726812
]
Otto Fowler commented on NIFI-5892:
-----------------------------------
[~laashe], [~ijokarumawak] patch pr submitted
> Wait timestamp lingers, potentially messing up downstream wait-notify pairs
> ---------------------------------------------------------------------------
>
> Key: NIFI-5892
> URL: https://issues.apache.org/jira/browse/NIFI-5892
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Lars Birger Aasheim
> Assignee: Otto Fowler
> Priority: Minor
> Labels: patch-available
> Attachments: TestLingeringWaitTimestamps.xml
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The Wait processor makes use of the attribute "wait.start.timestamp" to keep
> track of when it first encountered a flowfile. The observed behaviour is that
> this attribute is set only if it does not exist, if else it is just checked
> against the current time. With several wait-notify pairs in succession, there
> is a likelihood that a flowfile will be routed directly to "expired" in one
> of the downstream Wait processors due to a timestamp set upstream of it. I
> suggest allowing an option of deleting the timestamp once a file is routed to
> success (and perhaps also to expired). Currently I do this manually with an
> UpdateAttribute processor.
>
> Attached is a template with necessary components and also an explanation of
> how to reproduce the issue.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
