Why mappings define document structure in Elasticsearch - Visual Breakdown

Concept Flow - Why mappings define document structure

Define Mapping

↓

Set Field Types

↓

Index Document

↓

Elasticsearch Uses Mapping

↓

Store & Search Data Correctly

↓

Return Accurate Search Results

Mapping sets rules for fields before adding data, so Elasticsearch knows how to store and search documents.

Execution Sample

Elasticsearch

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

This code creates an index with a mapping that defines 'name' as text and 'age' as integer.

Execution Table

Step	Action	Mapping State	Document Indexed	Effect
1	Create index with mapping	{"name":"text", "age":"integer"}	No	Mapping defines field types
2	Index document {"name":"Alice", "age":30}	{"name":"text", "age":"integer"}	{"name":"Alice", "age":30}	Fields stored with correct types
3	Search for age > 25	{"name":"text", "age":"integer"}	{"name":"Alice", "age":30}	Search uses mapping to compare numbers
4	Index document {"name":"Bob", "age":"thirty"}	{"name":"text", "age":"integer"}	Error	Mapping rejects wrong type
5	End	{"name":"text", "age":"integer"}	N/A	Mapping ensures data consistency

💡 Execution stops because mapping enforces field types and rejects wrong data.

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4	Final
mapping	{}	{"name":"text", "age":"integer"}	{"name":"text", "age":"integer"}	{"name":"text", "age":"integer"}	{"name":"text", "age":"integer"}	{"name":"text", "age":"integer"}
document	N/A	N/A	{"name":"Alice", "age":30}	{"name":"Alice", "age":30}	Error (invalid age type)	N/A

Key Moments - 2 Insights

Why does indexing a document with wrong field type cause an error?

Because the mapping defines the expected type (e.g., integer for 'age'), and Elasticsearch rejects data that doesn't match, as shown in step 4 of the execution_table.

How does mapping affect searching documents?

Mapping tells Elasticsearch how to interpret fields (like numbers or text), so searches like 'age > 25' work correctly, as seen in step 3.

Visual Quiz - 3 Questions

Look at the execution_table, what is the mapping type for the 'name' field after step 1?

A keyword

B integer

C text

D date

💡 Hint

Check the 'Mapping State' column in row for step 1.

At which step does Elasticsearch reject a document due to wrong field type?

A Step 4

B Step 2

C Step 3

D Step 5

💡 Hint

Look for 'Error' in the 'Document Indexed' column.

If the mapping did not define 'age' as integer, what would happen when searching 'age > 25'?

A Search would work correctly

B Search might fail or give wrong results

C Documents would be rejected on indexing

D Mapping would auto-correct the type

💡 Hint

Refer to step 3 where mapping guides search behavior.

Concept Snapshot

Mapping in Elasticsearch:
- Defines field names and types before indexing
- Ensures data consistency and correct storage
- Guides search and query behavior
- Rejects documents with wrong field types
- Essential for accurate and efficient search

Full Transcript

In Elasticsearch, mappings define the structure of documents by specifying field names and their data types before any data is added. This helps Elasticsearch know how to store and search the data correctly. For example, if 'age' is defined as an integer, Elasticsearch expects numbers for that field. When a document with the wrong type is indexed, Elasticsearch rejects it to keep data consistent. Mappings also help searches work properly, like comparing numbers for queries. This step-by-step trace shows how mapping is created, documents are indexed, and how mapping enforces rules and guides searching.