Boolean datatype

Boolean fields accept JSON true and false values, but can also accept strings and numbers which are interpreted as either true or false:

False values

false, "false", "off", "no", "0", "" (empty string), 0, 0.0

True values

Anything that isn’t false.

For example:

PUT my_index
{
  "mappings": {
    "my_type": {
      "properties": {
        "is_published": {
          "type": "boolean"
        }
      }
    }
  }
}

POST my_index/my_type/1
{
  "is_published": true 
}

GET my_index/_search
{
  "query": {
    "term": {
      "is_published": 1 
    }
  }
}

Indexing a document with a JSON true.

Querying for the document with 1, which is interpreted as true.

Aggregations like the terms aggregation use 1 and 0 for the key, and the strings "true" and "false" for the key_as_string. Boolean fields when used in scripts, return 1 and 0:

POST my_index/my_type/1
{
  "is_published": true
}

POST my_index/my_type/2
{
  "is_published": false
}

GET my_index/_search
{
  "aggs": {
    "publish_state": {
      "terms": {
        "field": "is_published"
      }
    }
  },
  "script_fields": {
    "is_published": {
      "script": "doc['is_published'].value" 
    }
  }
}

Inline scripts must be enabled for this example to work.

Parameters for boolean fields

The following parameters are accepted by boolean fields:

boost

Field-level index time boosting. Accepts a floating point number, defaults to 1.0.

doc_values

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.

index

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

null_value

Accepts any of the true or false values listed above. The value is substituted for any explicit null values. Defaults to null, which means the field is treated as missing.

store

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