[NIFI-5448] Failed EL date parsing live-locks processors without a failure relationship

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Component/s: Core Framework
• Assignee: Mike Thomsen
• Reporter: David Koster
• Created: 23/Jul/18 15:21
• Updated: 15/Mar/24 15:21
• Resolved: 09/Feb/24 22:56

Description

Processors that utilize the Expression Language need to always present a failure relationship.

If a processor with only a success relationship, for example UpdateAttribute, utilizes the expression language to perform type coercion to a date and fails, the processor will be unable to dispose of the FlowFile and remain blocked indefinitely.

Recreation flow:

GenerateFlowFile -> Update Attribute #1 -> Update Attribute #2 -> Anything

Update Attribute #1 - test = "Hello World"

Update Attribute #2 - test = ${test:toDate('yyyy-MM-dd')}

 

Generates an IllegalAttributeException on UpdateAttribute.

 

The behavior should match numerical type coercion and silently skip the processing or offer failure relationships on processors supporting EL

Issue Links

• is related to: NIFI-6028 Upgrading NiFi can put versioned flows into a conflict state
• is related to: NIFI-6344 Add Failure Relationship to UpdateAttribute
• relates to: NIFI-12882 Allow control over unexpected failure behavior in processors
• relates to: NIFI-10396 Expression Language jsonPath throws error instead of returning empty string when subject is invalid JSON
• supercedes: NIFI-813 UpdateAttribute does not have a failure relationship for handling EL failures
• links to: GitHub Pull Request #2914