[NIFI-5892] Wait timestamp lingers, potentially messing up downstream wait-notify pairs

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 1.9.0
• Labels: patch-available
• Flags: Patch
• Assignee: Otto Fowler
• Reporter: Lars Birger Aasheim
• Created: 12/Dec/18 11:43
• Updated: 28/Dec/18 01:32
• Resolved: 28/Dec/18 01:32

Description

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.

Issue Links

• links to: GitHub Pull Request #3233