Routes FlowFiles based on their Attributes using the Attribute Expression Language

Additional Details...


attributes, routing, Attribute Expression Language, regexp, regex, Regular Expression, Expression Language, find, text, string, search, filter, detect


In the list below, the names of required properties appear in bold. Any other properties (not in bold) are considered optional. The table also indicates any default values.

Display NameAPI NameDefault ValueAllowable ValuesDescription
Routing StrategyRouting StrategyRoute to Property name
  • Route to Property name A copy of the FlowFile will be routed to each relationship whose corresponding expression evaluates to 'true'
  • Route to 'matched' if all match Requires that all user-defined expressions evaluate to 'true' for the FlowFile to be considered a match
  • Route to 'matched' if any matches Requires that at least one user-defined expression evaluate to 'true' for the FlowFile to be considered a match
Specifies how to determine which relationship to use when evaluating the Expression Language

Dynamic Properties:

Supports Sensitive Dynamic Properties: No

Dynamic Properties allow the user to specify both the name and value of a property.

Relationship NameAttribute Expression LanguageRoutes FlowFiles whose attributes match the Attribute Expression Language specified in the Dynamic Property Value to the Relationship specified in the Dynamic Property Key
Supports Expression Language: true (will be evaluated using flow file attributes and variable registry)


unmatchedFlowFiles that do not match any user-define expression will be routed here

Dynamic Relationships:

A Dynamic Relationship may be created based on how the user configures the Processor.

Name from Dynamic PropertyFlowFiles that match the Dynamic Property's Attribute Expression Language

Reads Attributes:

None specified.

Writes Attributes:

RouteOnAttribute.RouteThe relation to which the FlowFile was routed

State management:

This component does not store state.


This component is not restricted.

Input requirement:

This component requires an incoming relationship.

System Resource Considerations:

None specified.