WARNING: Version 6.1 of Elasticsearch has passed its EOL date.
This documentation is no longer being maintained and may be removed. If you are running this version, we strongly advise you to upgrade. For the latest information, see the current release documentation.
Simple Pattern Split Tokenizer
editSimple Pattern Split Tokenizer
editThis functionality is marked as experimental in Lucene
The simple_pattern_split
tokenizer uses a regular expression to split the
input into terms at pattern matches. The set of regular expression features it
supports is more limited than the pattern
tokenizer, but the tokenization is generally faster.
This tokenizer does not produce terms from the matches themselves. To produce
terms from matches using patterns in the same restricted regular expression
subset, see the simple_pattern
tokenizer.
This tokenizer uses Lucene regular expressions. For an explanation of the supported features and syntax, see Regular Expression Syntax.
The default pattern is the empty string, which produces one term containing the full input. This tokenizer should always be configured with a non-default pattern.
Configuration
editThe simple_pattern_split
tokenizer accepts the following parameters:
|
A Lucene regular expression, defaults to the empty string. |
Example configuration
editThis example configures the simple_pattern_split
tokenizer to split the input
text on underscores.
PUT my_index { "settings": { "analysis": { "analyzer": { "my_analyzer": { "tokenizer": "my_tokenizer" } }, "tokenizer": { "my_tokenizer": { "type": "simple_pattern_split", "pattern": "_" } } } } } POST my_index/_analyze { "analyzer": "my_analyzer", "text": "an_underscored_phrase" }
The above example produces these terms:
[ an, underscored, phrase ]