Joe There is another PR for route text...
Thanks Joe On Feb 25, 2016 3:41 PM, "Joseph Percivall (JIRA)" <[email protected]> wrote: > > [ > https://issues.apache.org/jira/browse/NIFI-1256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel > ] > > Joseph Percivall updated NIFI-1256: > ----------------------------------- > Attachment: Testing_NIFI-1256.xml > > Template used for testing > > > 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) >
