nifi-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Payne (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (NIFI-1256) Allow RouteText to use Expression Language to route lines
Date Tue, 23 Feb 2016 17:51:18 GMT

     [ https://issues.apache.org/jira/browse/NIFI-1256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Mark Payne updated NIFI-1256:
-----------------------------
    Attachment: 0001-NIFI-1256-Added-a-Satisfies-Expression-option-for-Ma.patch

> 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
>             Fix For: 0.6.0
>
>         Attachments: 0001-NIFI-1256-Added-a-Satisfies-Expression-option-for-Ma.patch
>
>
> 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)

Mime
View raw message