February 19, 2018 3:48 PM
To: users@nifi.apache.org<mailto:users@nifi.apache.org>
Subject: Re: Routing Files Based on Dynamic Pattern Matching
Maybe take a look at one of the ScanContent/Attribute processors? It allows to
map in a reloadable external file.
Or, better yet, one of the LookupSer
ent:* Monday, February 19, 2018 3:48 PM
> *To:* users@nifi.apache.org
> *Subject:* Re: Routing Files Based on Dynamic Pattern Matching
>
>
>
> Maybe take a look at one of the ScanContent/Attribute processors? It
> allows to map in a reloadable external file.
>
>
>
Shawn
From: Juan Sequeiros <helloj...@gmail.com>
Sent: Monday, February 19, 2018 4:14 PM
To: users@nifi.apache.org
Subject: Re: Routing Files Based on Dynamic Pattern Matching
You could also RouteOnAttribute [1] doing the same regular expression checks
using NIFI expression langu
You could also RouteOnAttribute [1] doing the same regular
expression checks using NIFI expression language [2].
For instance, I can create a route for "DATA A" if my attribute "filename"
matches a regular expression.
${filename:find'SomeJavaRegEx')}
If you can control your workflow maybe bring
bruary 19, 2018 3:48 PM
To: users@nifi.apache.org
Subject: Re: Routing Files Based on Dynamic Pattern Matching
Maybe take a look at one of the ScanContent/Attribute processors? It allows to
map in a reloadable external file.
Or, better yet, one of the LookupService variants, which is more generic
Maybe take a look at one of the ScanContent/Attribute processors? It allows
to map in a reloadable external file.
Or, better yet, one of the LookupService variants, which is more generic.
HTH,
Andrew
On Mon, Feb 19, 2018, 3:10 PM Shawn Weeks wrote:
> Hi, I’m looking
Hi, I'm looking for some ideas on how to handle a workflow I'm developing. I
have NiFi monitoring a drop off location where files are delivered. Files from
this drop off location need to be routed to various target directories based on
a series of file name patterns. Currently I have a custom