Getting a mapping
After setting our mappings for processing types, we may need to control or analyze the mapping to prevent issues such as wrong type detection, new fields being created due to a data mismatch, and broken index template configurations.
How we get the mapping for a type helps us understand its structure or evolution due to some merging and implicit type guessing.
Getting ready
You will need an up-and-running Elasticsearch installation, as we described in the Downloading and installing Elasticsearch recipe of Chapter 1, Getting Started.
To execute the commands in this recipe, you can use any HTTP clients, such as curl (https://curl.haxx.se/), Postman (https://www.getpostman.com/), or others. I suggest using the Kibana console as it provides code completion and better character escaping for Elasticsearch.
To execute the following commands correctly, you will need the mapping we created in the Putting a mapping in an index recipe.
How to do it...
The...
