Index mappings overview in Elasticsearch - Step-by-Step Execution

Concept Flow - Index mappings overview

Define index name

↓

Specify mappings

↓

Set field types

↓

Apply settings

↓

Create index with mappings

↓

Index documents

↓

Search uses mappings for queries

This flow shows how you define an index with mappings, set field types, create the index, and then index documents that use those mappings for searching.

Execution Sample

Elasticsearch

{
  "mappings": {
    "properties": {
      "name": {"type": "text"},
      "age": {"type": "integer"}
    }
  }
}

This JSON defines an index mapping with two fields: 'name' as text and 'age' as integer.

Execution Table

Step	Action	Input/Value	Result/State
1	Define index name	"users"	Index name set to 'users'
2	Specify mappings	{"name": {"type": "text"}, "age": {"type": "integer"}}	Mappings prepared with field types
3	Create index with mappings	Index name + mappings	Index 'users' created with specified mappings
4	Index document	{"name": "Alice", "age": 30}	Document stored with fields typed as per mappings
5	Search document	Query on 'name' field	Search uses 'text' type mapping for full-text search
6	Search document	Query on 'age' field	Search uses 'integer' type mapping for numeric queries
7	End	No more actions	Index ready for queries with correct field types

💡 All steps completed; index created and documents indexed using mappings

Variable Tracker

Variable	Start	After Step 2	After Step 3	After Step 4	Final
index_name	undefined	"users"	"users"	"users"	"users"
mappings	undefined	{"name": {"type": "text"}, "age": {"type": "integer"}}	{"name": {"type": "text"}, "age": {"type": "integer"}}	{"name": {"type": "text"}, "age": {"type": "integer"}}	{"name": {"type": "text"}, "age": {"type": "integer"}}
documents	empty	empty	empty	[{"name": "Alice", "age": 30}]	[{"name": "Alice", "age": 30}]

Key Moments - 2 Insights

Why do we need to specify field types in mappings?

Field types tell Elasticsearch how to store and search data. For example, 'text' fields are for full-text search, while 'integer' fields are for numbers. See execution_table step 2 and 5.

What happens if we index a document with a field not defined in mappings?

Elasticsearch tries to guess the field type dynamically, but this can cause inconsistent data types. Defining mappings upfront avoids this. Refer to variable_tracker documents after step 4.

Visual Quiz - 3 Questions

Look at the execution_table, what is the index name after step 3?

A "documents"

B "mappings"

C "users"

D "undefined"

💡 Hint

Check the 'Result/State' column in row for step 3 in execution_table

At which step does the document get stored in the index?

A Step 4

B Step 5

C Step 2

D Step 6

💡 Hint

Look for 'Document stored' in the 'Result/State' column in execution_table

If we add a new field without updating mappings, what might happen?

A Elasticsearch rejects the document

B Elasticsearch guesses the field type dynamically

C The index name changes

D The document is deleted

💡 Hint

Refer to key_moments about dynamic field type guessing

Concept Snapshot

Index mappings define field names and types in Elasticsearch.
They control how data is stored and searched.
Create an index with mappings before adding documents.
Mappings improve search accuracy and performance.
Dynamic mapping guesses types but can cause issues.
Always specify mappings for important fields.

Full Transcript

This visual execution shows how Elasticsearch index mappings work. First, you define the index name, then specify mappings with field types like text or integer. Next, you create the index with these mappings. When you index documents, Elasticsearch stores fields according to the mappings. Searches then use these types to run queries correctly. The execution table traces each step, showing how variables like index name, mappings, and documents change. Key moments clarify why field types matter and what happens if you add fields without mappings. The quiz tests understanding of index name, document storage step, and dynamic mapping behavior. The snapshot summarizes the core idea: mappings define how data is stored and searched in Elasticsearch indexes.