@MattWho Hi Matt, Many thanks for sharing your views. Please see my replies below to your questions: - It may be helpful if you shared your RouteText processor configuration. --> I have the exact same configuration as stated in your image. But instead of "lines", I gave the attribute name as "matched". Thats the only difference. (Pardon me for not able to share the actual image as the system in which I did was the actual server not having the internet connection) - 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. --> Yes - 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. --> Yes, thats correct. It would omit lines 2 and 15 but I need them as well. But if you see, the line * 2 abc-rr1-0 35185 20-Dec 03:43:54 Has a space after " * " and then the digit 2. But for the line: *15 abc-lr2-0 34686 20-Dec 03:43:54 there is no space after the " * " and then comes the digit 15. Hence to include this, I reconfigured the regex expression again as shared below: (\s|[ \t]|\*)\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} Please see the below link for the regex I made (not sure if you like it 😞 but I tried) https://regex101.com/r/pdo6Ca/1 2. I noticed you sample data has leading and trailing whitespace so make sure processor is configured to ignore those. --> I reworked on the regex again whose link is above to include/ignore those(https://regex101.com/r/pdo6Ca/1 ) Please share your views if this regex is wrong. 3. Since you intent is produce a new FlowFile with only the lines matching the regex, make sure you set the above Routing Strategy. --> Yes, it is set exactly as stated in your image but instead of creating one flow file with all matched lines, it creates multiple flow files with each matched lines printed in each same name flow file....multiple times, that too, sent to "unmatched" relationship 4. Make sure the correct matching strategy is selected. Should be what I have above. --> Yes, it is set exactly as stated in your image 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. --> Yes, correct 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. --> I had double checked and no extra return is there After all this, the issue I am having is that, when the flow file is sent to this processor, it is not sending any flow file values to the "lines" relationship or "matched" relationship (name I set in my processor). Instead, there happens two things: - It creates same flow file name (e.g. abc.txt) multiple times towards the "unmatched" relationship. So if the regex expression matches 7 lines from the input file coming from the previous processor, then it would create 7 abc.txt flow files routed towards "unmatched" relationship wherein each of those 7 files will contain 1 matched line each (different values captured I meant) - It creates 1 flow file sent to "original" relationship. It would be great if you can share your advise on the below aspect of mine: - It creates same flow file name (e.g. abc.txt) multiple times towards the "unmatched" relationship. So if the regex expression matches 7 lines from the input file coming from the previous processor, then it would create 7 abc.txt flow files routed towards "unmatched" relationship wherein each of those 7 files will contain 1 line each (different values captured I meant) Thank you again for your time and advise. Regards,
... View more
