NOTE: You are looking at documentation for an older release. For the latest information, see the current release documentation.

« norms position_increment_gap »

› › ›

null_value

edit

`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": {
    "_doc": {
      "properties": {
        "status_code": {
          "type":       "keyword",
          "null_value": "NULL" 
        }
      }
    }
  }
}

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

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

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

	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.

The null_value only influences how data is indexed, it doesn’t modify the _source document.

« norms position_increment_gap »