Our Community is getting an upgrade! To get everything ready for the relaunch, we’ll be placing the site in read-only mode starting September 21st.
We really appreciate your understanding while we get things set up behind the scenes. Catch up on all the exciting details about the move here.
Need help or have questions? Drop us a line at [email protected]
Created 05-13-2021 02:32 AM
Created on 05-13-2021 10:36 AM - edited 05-13-2021 10:37 AM
@sangee
The "RouteText" [1] processor is used to route individual lines within a multi-line content FlowFile to different relationships (essentially splitting up a multi-line FlowFile). What you are trying to accomplish can however be done using the "RouteOnContent" [2] processor.
Your sample shows content with two lines and only one of those lines containing the string "Merging completed". So I assume the other FlowFIle's content will have only one line with "Merging complete"?
If so, the "RouteOnContent" can be configured as follows:
The dynamic property I added becomes a new relationship on the processor. So any FlowFile where content matches exactly "Merging complete" will be sent to this relationship while all other FlowFiles will be routed to the pre-existing "unmatched" relationship.
[1] http://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.13.2/org.apache...
If you found this help with your query, please take a moment to login and click accept on this solution.
Thank you,
Matt
Created on 05-13-2021 10:36 AM - edited 05-13-2021 10:37 AM
@sangee
The "RouteText" [1] processor is used to route individual lines within a multi-line content FlowFile to different relationships (essentially splitting up a multi-line FlowFile). What you are trying to accomplish can however be done using the "RouteOnContent" [2] processor.
Your sample shows content with two lines and only one of those lines containing the string "Merging completed". So I assume the other FlowFIle's content will have only one line with "Merging complete"?
If so, the "RouteOnContent" can be configured as follows:
The dynamic property I added becomes a new relationship on the processor. So any FlowFile where content matches exactly "Merging complete" will be sent to this relationship while all other FlowFiles will be routed to the pre-existing "unmatched" relationship.
[1] http://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.13.2/org.apache...
If you found this help with your query, please take a moment to login and click accept on this solution.
Thank you,
Matt
Created 05-13-2021 08:16 PM