Token count datatypeedit

A field of type token_count is really an integer field which accepts string values, analyzes them, then indexes the number of tokens in the string.

For instance:

PUT my_index
  "mappings": {
    "_doc": {
      "properties": {
        "name": { 
          "type": "text",
          "fields": {
            "length": { 
              "type":     "token_count",
              "analyzer": "standard"

PUT my_index/_doc/1
{ "name": "John Smith" }

PUT my_index/_doc/2
{ "name": "Rachel Alice Williams" }

GET my_index/_search
  "query": {
    "term": {
      "name.length": 3 

The name field is an analyzed string field which uses the default standard analyzer.

The name.length field is a token_count multi-field which will index the number of tokens in the name field.

This query matches only the document containing Rachel Alice Williams, as it contains three tokens.

Parameters for token_count fieldsedit

The following parameters are accepted by token_count fields:


The analyzer which should be used to analyze the string value. Required. For best performance, use an analyzer without token filters.


Indicates if position increments should be counted. Set to false if you don’t want to count tokens removed by analyzer filters (like stop). Defaults to true.


Mapping field-level query time boosting. Accepts a floating point number, defaults to 1.0.


Should the field be stored on disk in a column-stride fashion, so that it can later be used for sorting, aggregations, or scripting? Accepts true (default) or false.


Should the field be searchable? Accepts not_analyzed (default) and no.


Accepts a numeric value of the same type as the field which is substituted for any explicit null values. Defaults to null, which means the field is treated as missing.


Whether the field value should be stored and retrievable separately from the _source field. Accepts true or false (default).