[
https://issues.apache.org/jira/browse/NIFI-1256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15167834#comment-15167834
]
Joseph Percivall commented on NIFI-1256:
----------------------------------------
Aside from one misspelling (line 118 misspelled Expression as "Expresision"),
patch looks good. I read through the code and then did a contrib check build. I
ran through multiple scenarios using a tester template (will attach to ticket).
I will fix the misspelling in the patch and merge it in.
+1, Thanks Mark!
> Allow RouteText to use Expression Language to route lines
> ---------------------------------------------------------
>
> Key: NIFI-1256
> URL: https://issues.apache.org/jira/browse/NIFI-1256
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Reporter: Mark Payne
> Assignee: Mark Payne
> Fix For: 0.6.0
>
> Attachments:
> 0001-NIFI-1256-Added-a-Satisfies-Expression-option-for-Ma.patch,
> Testing_NIFI-1256.xml
>
>
> As part of NIFI-1249, we made it so that Processors can provide their own
> 'variables' to be evaluated by the Expression Language. We should update
> RouteText to add a Matching Strategy of "Satisfies Expression". If this is
> selected, the values of user-defined properties should be required to be
> Expression Language Expressions that return BOOLEAN, as with RouteOnAttribute.
> We would add a variable named "line" so that users can route by using an
> expression like: ${line:toUpper():startsWith("U")}
> This is a much more powerful mechanism than the others, as it allows any and
> all of the existing strategies to be combined into a single expression and
> allows users to use different types of comparisons for each property.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
