[
https://issues.apache.org/jira/browse/NIFI-5448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16554215#comment-16554215
]
ASF GitHub Bot commented on NIFI-5448:
--------------------------------------
Github user MikeThomsen commented on the issue:
https://github.com/apache/nifi/pull/2914
In case any reviewer comes along and wonders why it wouldn't be simpler to
just control the EL logic and input data better, the reason why is that the
folks in our company who reported this error to me and @dmkoster are working
with another team that is driving this with their own input. So their only
choices in this multiple-chefs-in-the-kitchen situation are to either add
manual steps to clean it up or watch the data back up in the queue.
> Failed EL date parsing live-locks processors without a failure relationship
> ---------------------------------------------------------------------------
>
> Key: NIFI-5448
> URL: https://issues.apache.org/jira/browse/NIFI-5448
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Reporter: David Koster
> Assignee: Mike Thomsen
> Priority: Major
>
> 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
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
