Boolean field type

Boolean field type

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

False values

false, “false”, “” (empty string)

True values

true, “true”

For example:

  1. PUT my-index-000001
  2. {
  3.   "mappings": {
  4.     "properties": {
  5.       "is_published": {
  6.         "type": "boolean"
  7.       }
  8.     }
  9.   }
  10. }
  12. POST my-index-000001/_doc/1?refresh
  13. {
  14.   "is_published": "true" 
  15. }
  17. GET my-index-000001/_search
  18. {
  19.   "query": {
  20.     "term": {
  21.       "is_published": true 
  22.     }
  23.   }
  24. }

Indexing a document with “true”, which is interpreted as true.

Searching for documents with a JSON 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 true and false:

  1. POST my-index-000001/_doc/1?refresh
  2. {
  3.   "is_published": true
  4. }
  6. POST my-index-000001/_doc/2?refresh
  7. {
  8.   "is_published": false
  9. }
  11. GET my-index-000001/_search
  12. {
  13.   "aggs": {
  14.     "publish_state": {
  15.       "terms": {
  16.         "field": "is_published"
  17.       }
  18.     }
  19.   },
  20.   "sort": [ "is_published" ],
  21.   "fields": [
  22.     {"field": "weight"}
  23.   ],
  24.   "runtime_mappings": {
  25.     "weight": {
  26.       "type": "long",
  27.       "script": "emit(doc['is_published'].value ? 10 : 0)"
  28.     }
  29.   }
  30. }

Parameters for boolean fields

The following parameters are accepted by boolean fields:

boost

Mapping field-level query 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 true (default) and false.

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. Note that this cannot be set if the script parameter is used.

on_script_error

Defines what to do if the script defined by the script parameter throws an error at indexing time. Accepts fail (default), which will cause the entire document to be rejected, and continue, which will register the field in the document’s _ignored metadata field and continue indexing. This parameter can only be set if the script field is also set.

script

If this parameter is set, then the field will index values generated by this script, rather than reading the values directly from the source. If a value is set for this field on the input document, then the document will be rejected with an error. Scripts are in the same format as their runtime equivalent.

store

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

meta

Metadata about the field.