diff --git a/docs/reference/analysis/tokenfilters/trim-tokenfilter.asciidoc b/docs/reference/analysis/tokenfilters/trim-tokenfilter.asciidoc index 1373811b0cb82..19d47f203afb8 100644 --- a/docs/reference/analysis/tokenfilters/trim-tokenfilter.asciidoc +++ b/docs/reference/analysis/tokenfilters/trim-tokenfilter.asciidoc @@ -4,4 +4,107 @@ Trim ++++ -The `trim` token filter trims the whitespace surrounding a token. +Removes leading and trailing whitespace from each token in a stream. + +The `trim` filter uses Lucene's +https://lucene.apache.org/core/{lucene_version_path}/analyzers-common/org/apache/lucene/analysis/miscellaneous/TrimFilter.html[TrimFilter]. + +[TIP] +==== +Many commonly used tokenizers, such as the +<> or +<> tokenizer, remove whitespace by +default. When using these tokenizers, you don't need to add a separate `trim` +filter. +==== + +[[analysis-trim-tokenfilter-analyze-ex]] +==== Example + +To see how the `trim` filter works, you first need to produce a token +containing whitespace. + +The following <> request uses the +<> tokenizer to produce a token for +`" fox "`. + +[source,console] +---- +GET _analyze +{ + "tokenizer" : "keyword", + "text" : " fox " +} +---- + +The API returns the following response. Note the `" fox "` token contains +the original text's whitespace. + +[source,console-result] +---- +{ + "tokens": [ + { + "token": " fox ", + "start_offset": 0, + "end_offset": 5, + "type": "word", + "position": 0 + } + ] +} +---- + +To remove the whitespace, add the `trim` filter to the previous analyze API +request. + +[source,console] +---- +GET _analyze +{ + "tokenizer" : "keyword", + "filter" : ["trim"], + "text" : " fox " +} +---- + +The API returns the following response. The returned `fox` token does not +include any leading or trailing whitespace. + +[source,console-result] +---- +{ + "tokens": [ + { + "token": "fox", + "start_offset": 0, + "end_offset": 5, + "type": "word", + "position": 0 + } + ] +} +---- + +[[analysis-trim-tokenfilter-analyzer-ex]] +==== Add to an analyzer + +The following <> request uses the `trim` +filter to configure a new <>. + +[source,console] +---- +PUT trim_example +{ + "settings": { + "analysis": { + "analyzer": { + "keyword_trim": { + "tokenizer": "keyword", + "filter": [ "trim" ] + } + } + } + } +} +---- \ No newline at end of file