It may be helpful if you shared your RouteText processor configuration.
Correct me if I am wrong, but you are looking to have all lines (minus the header lines) placed in a new FlowFile by themselves.
Using you example data and the regex you provided.
wwwwww aa cc
# Name foo Since ddd/www dddd
-- --------- ----- --------------- --- --- ---------
0 abc-lr1-0 35189 20-Dec 03:43:54
1 abc-rr2-g 35209 20-Dec 03:43:54
* 2 abc-rr1-0 35185 20-Dec 03:43:54
* 15 abc-lr2-0 34686 20-Dec 03:43:54
16 abc-lr1-0 34631 20-Dec 03:43:54
The above would result in a FlowFile with only lines 0,1, and 16. The header plus lines 2 and 15 would route to unmatched because of the leading "*" which does not match your regex.
Result would be a FlowFile with:
0 abc-lr1-0 35189 20-Dec 03:43:54
1 abc-rr2-g 35209 20-Dec 03:43:54
16 abc-lr1-0 34631 20-Dec 03:43:54
Couple things to check if what you are seeing is entire original FlowFile getting routed to the "Original" and "Unmatched" relationships:
1. RouteText processor configuration. If i understand your use case correctly, it should be configured like this:
2. I noticed you sample data has leading and trailing whitespace so make sure processor is configured to ignore those.
3. Since you intent is produce a new FlowFile with only the lines matching the regex, make sure you set the above Routing Strategy.
4. Make sure the correct matching strategy is selected. Should be what I have above.
5. Click on the "+" to add a new dynamic property for your regex, The property name becomes a new relationship on the processor where your matching lines will be routed.
6. Since you are evaluating the source FlowFile content line-by-line, make sure your regex does not have a line return at the end of it.
Correct:
Incorrect (notice the line 2 which indicates a line return at end of regex):
When I ran a little test flow using your sample data and regex, I got the desired results:
The "lines" relationship has one new FlowFile with content of only the 3 matching lines
The "unmatched" relationship contains a new FlowFile with content containing all the unmatched lines.
The "original" relationship contains the original FlowFile that was processed by this processor.
If you don't care about the original or unmatched FlowFiles, you can simply auto-terminate those relationships instead of routing them out of the processor in connections as I did above.
Hope this helps,
Matt
RouteText does not modify the content of the lines. It only routes lines to different produced new FlowFiles. The content of those lines remains unchanged. The RouteText processor also does nothing with capture groups, so the entire regex is going to be evaluated against each line.
I took the entire content from your "https://regex101.com/r/pdo6Ca/1" and the entire new regex from same and ran this flow.
I produced only one source FlowFile as you can see processor in = 1
You can see it routed "out" three FlowFiles.
One to the connection with the "matched" relationship which contains only one line since only one line matched the entire regex. (regex101 is taking in to account your capture groups)
If you change:
And run same test again, you will see a few more lines match (those with the additional "yes yes ..." in the lines).
I attached template i used which you can import to your NiFi.
Community does not support .xml files so i changed extension to .txt. You will need to change extension back to .xml before you can import the template in to your NiFi.
Hope this helps.
I am not able to reproduce the 1file in and 7 files out that you described.
Are you sure it is only 1 FlowFile in?
As far as your use case goes, perhaps you use RouteText first to produce the new FlowFile with all the lines containing the data you want (This includes the leading "*" and trailing "yes yes ..." strings).
To do this you would use the following regex and a "matching strategy" of "contains regular expression":
\d{1,2}\s\w{1,4}\-\w{1,4}\-(\w{1,2}|\w{0})\s\d{1,5}\s\d{1,2}\-\w{1,3}\s\d{1,2}\:\d{1,2}\:\d{1,2}
Then pass that new FlowFile to a ReplaceText processor which can trim off the leading whitespaces and "*" and any trailing whitespace characters and additional text. This ReplaceText would be configured as follows:
And use Search Value of which contains 3 capture groups:
(.*?)(\d{1,2}\s\w{1,4}\-\w{1,4}\-(\w{1,2}|\w{0})\s\d{1,5}\s\d{1,2}\-\w{1,3}\s\d{1,2}\:\d{1,2}\:\d{1,2})(.*?)$The processor replaces text line-by-line with only the second capture group.
This worked for me to get the end result of:
Which is what i believe you are looking for in the resulting FlowFile's content.
Hope this helps,
Matt
