Index mapping and text analysis
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
As part of planning how your incoming data might be transformed and enriched as it is ingested, you may want to customize how the data should be organized inside Elasticsearch and how text fields should be analyzed.
Refer to Mapping to learn about the dynamic mapping rules that Elasticsearch runs by default to identify the data types in your data and to store it in matching fields. You can also configure your own custom mappings to take full control over how your data is organized in the documents in an Elasticsearch index.
Refer to Text analysis to learn how to configure an analyzer to run on incoming text, in order to ensure that relevant documents are retrieved from text-based queries. You can opt to use one of several built-in analyzers, or create a custom analyzer for your specific use cases.