Document metadata fields
Elastic Cloud Serverless projects are autoscaled environments, fully managed by Elastic and available on Elastic Cloud. Availability This functionality is generally available and ready for production usage. Serverless interfaces and procedures might differ from classic Elastic Stack deployments. The Elastic Stack includes Elastic's core products such as Elasticsearch, Kibana, Logstash, and Beats. Availability This functionality is generally available and ready for production usage. Unless stated otherwise on the page, this functionality is available when your Elastic Stack is deployed on Elastic Cloud Hosted, Elastic Cloud Enterprise, Elastic Cloud on Kubernetes, and self-managed environments. This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes.
Serverless
Generally available
Stack
Generally available
Each document has metadata associated with it, such as the _index and _id metadata fields. The behavior of some of these metadata fields can be customized when a mapping is created.
_source- The original JSON representing the body of the document.
_size- The size of the
_sourcefield in bytes, provided by themapper-sizeplugin.
_doc_count- A custom field used for storing doc counts when a document represents pre-aggregated data.
_field_names- All fields in the document which contain non-null values.
_ignored- All fields in the document that have been ignored at index time because of
ignore_malformed.
_routing- A custom routing value which routes a document to a particular shard.