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

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

Github user apiri commented on a diff in the pull request:

    https://github.com/apache/nifi/pull/2914#discussion_r210130185
  
    --- Diff: 
nifi-nar-bundles/nifi-update-attribute-bundle/nifi-update-attribute-processor/src/main/java/org/apache/nifi/processors/attributes/UpdateAttribute.java
 ---
    @@ -144,6 +149,21 @@ public ValidationResult validate(String subject, 
String input, ValidationContext
             }
         };
     
    +    public static final AllowableValue FAIL_STOP = new 
AllowableValue("stop", "Penalize", "Penalize FlowFiles." +
    --- End diff --
    
    Hey @MikeThomsen,
    This was a little confusing when I did a build and was configuring the 
processor.  What do you think of making this penalize instead of stop.  At 
first I thought I was missing an option in the drop down.  While the value is 
supposed to be dev facing and the display property is user facing, the tooltips 
in the UI make use of the value and not the display property.  


> 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
>             Fix For: 1.8.0
>
>
> 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