[
https://issues.apache.org/jira/browse/NIFI-10853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17649671#comment-17649671
]
Jens M Kofoed commented on NIFI-10853:
--------------------------------------
The RouteOnAttribute takes in an expression language, and therefore test if the
string is a valid EL.
The UpdateAttribute takes both EL and free text and the string is a valid free
text. I've been there my self many times, missing something.
Looking forward to the new EL validator
> UpdateAttribute - expression language syntax error not caught until processor
> runtime
> -------------------------------------------------------------------------------------
>
> Key: NIFI-10853
> URL: https://issues.apache.org/jira/browse/NIFI-10853
> Project: Apache NiFi
> Issue Type: Bug
> Reporter: Nissim Shiman
> Assignee: Nissim Shiman
> Priority: Major
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> The UpdateAttribute will not show any alerts when the following expression
> language value is used for a property value:
> {code:java}
> ${filename:equals('testFile'}
> {code}
> This is also true when using the 'Verify Properties' button. (A green arrow
> is returned saying "Component Validation Passed").
> The processor will start, but when a flowfile passed through on runtime,
> though, it will fail
> with error
> {code}
> org.apache.nifi.attribute.expression.language.exception.AttributeExpressionLanguageException:
> Invalid Expression: ${filename:equals('testFile'} due to Unexpected token
> '}' at line 1, column 28. Query: ${filename:equals(testFile}
> {code}
> (This is not the case with RouteOnAttribute, which will leave the processor
> in an invalid state, flagging this as an alert, until the expression is
> corrected.)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
