Evaluates one or more Regular Expressions against the content of a FlowFile. The results of those Regular Expressions are assigned to FlowFile Attributes. Regular Expressions are entered by adding user-defined properties; the name of the property maps to the Attribute Name into which the result will be placed. The value of the property must be a valid Regular Expressions with exactly one capturing group. If the Regular Expression matches more than once, only the first match will be used. If any provided Regular Expression matches, the FlowFile(s) will be routed to 'matched'. If no provided Regular Expression matches, the FlowFile will be routed to 'unmatched' and no attributes will be applied to the FlowFile.
Tags: evaluate, Text, Regular Expression, regex, experimental
Properties:
In the list below, the names of required properties appear in bold. Anyother properties (not in bold) are considered optional. The table also indicates any default values, whether a property supports the NiFi Expression Language (or simply EL), and whether a property is considered "sensitive", meaning that its value will be encrypted. Before entering a value in a sensitive property, ensure that the nifi.properties file has an entry for the property nifi.sensitive.props.key.
| Name | Description | Default Value | Valid Values | EL | Sensitive |
|---|---|---|---|---|---|
| Character Set | The Character Set in which the file is encoded | UTF-8 | No | No | |
| Maximum Buffer Size | Specifies the maximum amount of data to buffer (per file) in order to apply the regular expressions. Files larger than the specified maximum will not be fully evaluated. | 1 MB | No | No | |
| Enable Canonical Equivalence | Indicates that two characters match only when their full canonical decompositions match. | false |
| No | No |
| Enable Case-insensitive Matching | Indicates that two characters match even if they are in a different case. Can also be specified via the embeded flag (?i). | false |
| No | No |
| Permit Whitespace and Comments in Pattern | In this mode, whitespace is ignored, and embedded comments starting with # are ignored until the end of a line. Can also be specified via the embeded flag (?x). | false |
| No | No |
| Enable DOTALL Mode | Indicates that the expression '.' should match any character, including a line terminator. Can also be specified via the embeded flag (?s). | false |
| No | No |
| Enable Literal Parsing of the Pattern | Indicates that Metacharacters and escape characters should be given no special meaning. | false |
| No | No |
| Enable Multiline Mode | Indicates that '^' and '$' should match just after and just before a line terminator or end of sequence, instead of only the begining or end of the entire input. Can also be specified via the embeded flag (?m). | false |
| No | No |
| Enable Unicode-aware Case Folding | When used with 'Enable Case-insensitive Matching', matches in a manner consistent with the Unicode Standard. Can also be specified via the embeded flag (?u). | false |
| No | No |
| Enable Unicode Predefined Character Classes | Specifies conformance with the Unicode Technical Standard #18: Unicode Regular Expression Annex C: Compatibility Properties. Can also be specified via the embeded flag (?U). | false |
| No | No |
| Enable Unix Lines Mode | Indicates that only the ' ' line terminator is recognized int the behavior of '.', '^', and '$'. Can also be specified via the embeded flag (?d). | false |
| No | No |
Relationships:
| Name | Description |
|---|---|
| matched | FlowFiles are routed to this relationship when the Regular Expression is successfully evaluated and the FlowFile is modified as a result |
| unmatched | FlowFiles are routed to this relationship when no provided Regular Expression matches the content of the FlowFile |