Aldrin,
Wow, I was all set to push back on this, but I re-read what I'd once
found on NiFi Rocks (especially the highlighted sentence):
"This processor applies user-added regular expressions to the
content of a FlowFile and routes a copy of the FlowFile to each
destination whose regular expression matches. *The user adds
properties where the name is the relationship that the FlowFile
should follow if it matches the regular expression, which is defined
as the property’s value.* User-defined properties do support the
NiFi Expression Language, but in such cases, the results are
interpreted as literal values, not regular expressions."
which was suddenly hugely clearer when I read it after reading what you
wrote me here. The link you provide, for its sister processor (and with
which I have the experience of hundreds of times using it), was
misleading to the point that I thought for a moment to push back.
Once I'd digested the NiFi Rocks blurb, it fell into place. I don't know
if this constitutes a suggestion for /RouteOnContent/'s usage or not.
Now that I grok it, I don't need it, but the next poor schmuck? (Well,
I've already hit an all-time high for stupid questions this week --
;-) .)
Thanks!
Russ
P.S. Yeah, as the domain says, NiFi totally rocks!
On 03/30/2017 11:42 AM, Aldrin Piri wrote:
Russell,
Your expectations are inline with the functionality of the processor.
You can add dynamic relationship via a dynamic property in the
processor properties tab. The plus (+) located at the top right will
let you first specify a property name (Treated as the relationship)
and its value would be the regex of choice. After hitting apply, the
relationship will be available to connect to other components.
This is covered for RouteOnAttribute in the User Guide [1].
[1]
http://nifi.apache.org/docs/nifi-docs/html/user-guide.html#properties-tab
On Thu, Mar 30, 2017 at 1:32 PM, Russell Bateman
<[email protected] <mailto:[email protected]>> wrote:
I'm working in NiFi 1.1.1. In this processor's usage, I see:
Dynamic Relationships:
A Dynamic Relationship may be created based on how the user
configures the Processor.
Name Description
Name from Dynamic Property FlowFiles that match the Dynamic
Property's Regular Expression
However, I cannot see in configuration any option to create a
relationship other than the "unmatched" one that already exists.
I've connect up the "unmatched" route, but find no opportunity
before or during my attempt to wire the "matches" route to
anything (there isn't a "matches" route).
Have I misunderstood this processor's purpose?
Thanks.