WARNING: Version 2.1 of Elasticsearch has passed its EOL date.

This documentation is no longer being maintained and may be removed. If you are running this version, we strongly advise you to upgrade. For the latest information, see the current release documentation.

« norms position_increment_gap »

› › ›

null_value

edit

IMPORTANT: This documentation is no longer updated. Refer to Elastic's version policy and the latest documentation.

`null_value`

edit

A null value cannot be indexed or searched. When a field is set to null, (or an empty array or an array of null values) it is treated as though that field has no values.

The null_value parameter allows you to replace explicit null values with the specified value so that it can be indexed and searched. For instance:

PUT my_index
{
  "mappings": {
    "my_type": {
      "properties": {
        "status_code": {
          "type":       "string",
          "index":      "not_analyzed",
          "null_value": "NULL" 
        }
      }
    }
  }
}

PUT my_index/my_type/1
{
  "status_code": null
}

PUT my_index/my_type/2
{
  "status_code": [] 
}

GET my_index/_search
{
  "query": {
    "term": {
      "status_code": "NULL" 
    }
  }
}

Copy as curl View in Sense

	Replace explicit `null` values with the term `NULL`.
	An empty array does not contain an explicit `null`, and so won’t be replaced with the `null_value`.
	A query for `NULL` returns document 1, but not document 2.

The null_value needs to be the same datatype as the field. For instance, a long field cannot have a string null_value. String fields which are analyzed will also pass the null_value through the configured analyzer.

Also see the missing query for its null_value support.

« norms position_increment_gap »

Was this helpful?

Feedback