[ 
https://issues.apache.org/jira/browse/NIFI-5448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16558864#comment-16558864
 ] 

ASF GitHub Bot commented on NIFI-5448:
--------------------------------------

Github user mcgilman commented on the issue:

    https://github.com/apache/nifi/pull/2914
  
    I would be very careful taking that option. Yes, it would ensure that users 
flows remain valid. However, I would question if that is the behavior that 
those users actually want. If the new relationship were auto-terminated that 
would mean that any data routed there would be DROPped. Folks upgrading may not 
realize this and it could lead to data loss.
    
    This concern was brought up in an old JIRA [1]. At that time, the solution 
was to penalize the flowfile and rollback the session. Since this processor is 
so widely used, it may warrant a DISCUSS thread so the community can consider 
the options and when they may be appropriate to introduce.
    
    [1] https://issues.apache.org/jira/browse/NIFI-11


> 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)

Reply via email to