[NIFI-813] UpdateAttribute does not have a failure relationship for handling EL failures

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 0.2.1
• Component/s: Core Framework, Extensions
• Assignee: Unassigned
• Reporter: Aldrin Piri
• Created: 05/Aug/15 04:03
• Updated: 14/Aug/18 21:07
• Resolved: 14/Aug/18 20:18

Description

UpdateAttribute's genesis predates expression language, and as originally created would have made failure improbable (impossible?) in context of typical processing. As a result, when EL was introduced, there was also a means wherein the processor could fail. Currently, there is no failure relationship. As a result, the only way to remove files that are failing due to an EL issues and placed back onto the queue is through an expiration on the incoming connection. One particular instance is that of formatting a bad date input. Template showing example to follow.

It could be the case this is a deficiency in just this particular EL function, but should EL become an extension point, it is entirely conceivable that failure cases become an occurrence that needs to be handled.

Issue Links

• is superceded by: NIFI-5448 Failed EL date parsing live-locks processors without a failure relationship