Elasticsearch Metadata

By Opster Team

Updated: Mar 21, 2023

| 1 min read

Overview

Metadata in Elasticsearch refers to additional information stored for each document. This is achieved using the specific metadata fields available in Elasticsearch. The default behavior of some of these metadata fields can be customized during mapping creation.

Examples

Using _meta meta-field for storing application-specific information with the mapping:

PUT /my_index?pretty
{
  "mappings": {
    "_meta": { 
      "domain": "security",
      "release_information": {
        "date": "18-01-2020",
        "version": "7.5"
      }
    }
  }
}

Notes

  • In version 2.x, Elasticsearch had a total 13 meta fields available, which are: _index, _uid, _type, _id, _source, _size, _all, _field_names, _timestamp, _ttl, _parent, _routing, _meta
  • In version 5.x, _timestamp and _ttl meta fields were removed.
  • In version 6.x, the _parent meta field was removed.
  • In version 7.x, _uid and _all meta fields were removed.

How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?


Related log errors to this ES concept


Failed to set minimum value is not a number
Found old metadata state loading metadata from and converting to new metadata location and strucutre
Unexpected value for setting it should be dash delimited
Conversion to new metadata location and format done backup create at
Found old metadata state loading metadata from and converting to new metadata location and structure
Unexpected token while reading snapshot metadata
Byte-sized cluster setting with value is missing units assuming default units b but in future versions this will be a hard error
Byte-sized index setting with value is missing units assuming default units b but in future versions this will be a hard error
Time cluster setting with value is missing units assuming default units ms but in future versions this will be a hard error
Time index setting with value is missing units assuming default units ms but in future versions this will be a hard error
Unable to update lifecycle metadata with new ilm mode
Failed to build json for alias request

< Page: 10 of 15 >