Analyze API

Performs analysis on a text string and returns the resulting tokens.

  1. GET /_analyze
  2. {
  3.   "analyzer" : "standard",
  4.   "text" : "Quick Brown Foxes!"
  5. }

Request

GET /_analyze

POST /_analyze

GET /<index>/_analyze

POST /<index>/_analyze

Path parameters

<index>

(Optional, string) Index used to derive the analyzer.

If specified, the analyzer or <field> parameter overrides this value.

If no analyzer or field are specified, the analyze API uses the default analyzer for the index.

If no index is specified or the index does not have a default analyzer, the analyze API uses the standard analyzer.

Query parameters

analyzer

(Optional, string) The name of the analyzer that should be applied to the provided text. This could be a built-in analyzer, or an analyzer that’s been configured in the index.

If this parameter is not specified, the analyze API uses the analyzer defined in the field’s mapping.

If no field is specified, the analyze API uses the default analyzer for the index.

If no index is specified, or the index does not have a default analyzer, the analyze API uses the standard analyzer.

attributes

(Optional, array of strings) Array of token attributes used to filter the output of the explain parameter.

char_filter

(Optional, array of strings) Array of character filters used to preprocess characters before the tokenizer. See Character filters reference for a list of character filters.

explain

(Optional, boolean) If true, the response includes token attributes and additional details. Defaults to false. [experimental] The format of the additional detail information is labelled as experimental in Lucene and it may change in the future.

field

(Optional, string) Field used to derive the analyzer. To use this parameter, you must specify an index.

If specified, the analyzer parameter overrides this value.

If no field is specified, the analyze API uses the default analyzer for the index.

If no index is specified or the index does not have a default analyzer, the analyze API uses the standard analyzer.

filter

(Optional, Array of strings) Array of token filters used to apply after the tokenizer. See Token filter reference for a list of token filters.

normalizer

(Optional, string) Normalizer to use to convert text into a single token. See Normalizers for a list of normalizers.

text

(Required, string or array of strings) Text to analyze. If an array of strings is provided, it is analyzed as a multi-value field.

tokenizer

(Optional, string) Tokenizer to use to convert text into tokens. See Tokenizer reference for a list of tokenizers.

Examples

No index specified

You can apply any of the built-in analyzers to the text string without specifying an index.

  1. GET /_analyze
  2. {
  3.   "analyzer" : "standard",
  4.   "text" : "this is a test"
  5. }

Array of text strings

If the text parameter is provided as array of strings, it is analyzed as a multi-value field.

  1. GET /_analyze
  2. {
  3.   "analyzer" : "standard",
  4.   "text" : ["this is a test", "the second text"]
  5. }

Custom analyzer

You can use the analyze API to test a custom transient analyzer built from tokenizers, token filters, and char filters. Token filters use the filter parameter:

  1. GET /_analyze
  2. {
  3.   "tokenizer" : "keyword",
  4.   "filter" : ["lowercase"],
  5.   "text" : "this is a test"
  6. }
  1. GET /_analyze
  2. {
  3.   "tokenizer" : "keyword",
  4.   "filter" : ["lowercase"],
  5.   "char_filter" : ["html_strip"],
  6.   "text" : "this is a <b>test</b>"
  7. }

Custom tokenizers, token filters, and character filters can be specified in the request body as follows:

  1. GET /_analyze
  2. {
  3.   "tokenizer" : "whitespace",
  4.   "filter" : ["lowercase", {"type": "stop", "stopwords": ["a", "is", "this"]}],
  5.   "text" : "this is a test"
  6. }

Specific index

You can also run the analyze API against a specific index:

  1. GET /analyze_sample/_analyze
  2. {
  3.   "text" : "this is a test"
  4. }

The above will run an analysis on the “this is a test” text, using the default index analyzer associated with the analyze_sample index. An analyzer can also be provided to use a different analyzer:

  1. GET /analyze_sample/_analyze
  2. {
  3.   "analyzer" : "whitespace",
  4.   "text" : "this is a test"
  5. }

Derive analyzer from a field mapping

The analyzer can be derived based on a field mapping, for example:

  1. GET /analyze_sample/_analyze
  2. {
  3.   "field" : "obj1.field1",
  4.   "text" : "this is a test"
  5. }

Will cause the analysis to happen based on the analyzer configured in the mapping for obj1.field1 (and if not, the default index analyzer).

Normalizer

A normalizer can be provided for keyword field with normalizer associated with the analyze_sample index.

  1. GET /analyze_sample/_analyze
  2. {
  3.   "normalizer" : "my_normalizer",
  4.   "text" : "BaR"
  5. }

Or by building a custom transient normalizer out of token filters and char filters.

  1. GET /_analyze
  2. {
  3.   "filter" : ["lowercase"],
  4.   "text" : "BaR"
  5. }

Explain analyze

If you want to get more advanced details, set explain to true (defaults to false). It will output all token attributes for each token. You can filter token attributes you want to output by setting attributes option.

The format of the additional detail information is labelled as experimental in Lucene and it may change in the future.

  1. GET /_analyze
  2. {
  3.   "tokenizer" : "standard",
  4.   "filter" : ["snowball"],
  5.   "text" : "detailed output",
  6.   "explain" : true,
  7.   "attributes" : ["keyword"] 
  8. }

Set “keyword” to output “keyword” attribute only

The request returns the following result:

  1. {
  2.   "detail" : {
  3.     "custom_analyzer" : true,
  4.     "charfilters" : [ ],
  5.     "tokenizer" : {
  6.       "name" : "standard",
  7.       "tokens" : [ {
  8.         "token" : "detailed",
  9.         "start_offset" : 0,
  10.         "end_offset" : 8,
  11.         "type" : "<ALPHANUM>",
  12.         "position" : 0
  13.       }, {
  14.         "token" : "output",
  15.         "start_offset" : 9,
  16.         "end_offset" : 15,
  17.         "type" : "<ALPHANUM>",
  18.         "position" : 1
  19.       } ]
  20.     },
  21.     "tokenfilters" : [ {
  22.       "name" : "snowball",
  23.       "tokens" : [ {
  24.         "token" : "detail",
  25.         "start_offset" : 0,
  26.         "end_offset" : 8,
  27.         "type" : "<ALPHANUM>",
  28.         "position" : 0,
  29.         "keyword" : false 
  30.       }, {
  31.         "token" : "output",
  32.         "start_offset" : 9,
  33.         "end_offset" : 15,
  34.         "type" : "<ALPHANUM>",
  35.         "position" : 1,
  36.         "keyword" : false 
  37.       } ]
  38.     } ]
  39.   }
  40. }

Output only “keyword” attribute, since specify “attributes” in the request.

Setting a token limit

Generating excessive amount of tokens may cause a node to run out of memory. The following setting allows to limit the number of tokens that can be produced:

index.analyze.max_token_count

The maximum number of tokens that can be produced using _analyze API. The default value is 10000. If more than this limit of tokens gets generated, an error will be thrown. The _analyze endpoint without a specified index will always use 10000 value as a limit. This setting allows you to control the limit for a specific index:

  1. PUT /analyze_sample
  2. {
  3.   "settings" : {
  4.     "index.analyze.max_token_count" : 20000
  5.   }
  6. }
  1. GET /analyze_sample/_analyze
  2. {
  3.   "text" : "this is a test"
  4. }