[
https://issues.apache.org/jira/browse/NIFI-5892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16725653#comment-16725653
]
Lars Birger Aasheim commented on NIFI-5892:
-------------------------------------------
To solve the described problem, yes, but I guess there is no reason not to
remove all wait.* attributes upon routing to the success relationship. This
could be optional though, controlled by a true/false option in the processor.
Personally I think such an option should be set to true by default (remove
wait.* attributes).
> 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
> Attachments: TestLingeringWaitTimestamps.xml
>
>
> 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)
