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.

Practice

1. What is the main purpose of index mappings in Elasticsearch?

easy

A. To monitor server health

B. To create user accounts for Elasticsearch

C. To backup data automatically

D. To define how data fields are stored and searched

Solution

1. Step 1: Understand the role of index mappings

   Index mappings tell Elasticsearch how to store and interpret each field in your data.

2. Step 2: Compare options with this role

   Only To define how data fields are stored and searched matches this purpose; others relate to unrelated tasks.

3. Final Answer:

   To define how data fields are stored and searched -> Option D

4. Quick Check:

   Index mappings = data structure definition [OK]

Hint: Mappings control data structure and search behavior [OK]

Common Mistakes:

• Confusing mappings with user management
• Thinking mappings handle backups
• Assuming mappings monitor server health

2. Which of the following is the correct way to define a text field in an Elasticsearch mapping?

easy

A. "name": { "type": "text" }

B. "name": { "type": "keyword" }

C. "name": { "type": "integer" }

D. "name": { "type": "date" }

Solution

1. Step 1: Identify the correct field type for text data

   Text fields in Elasticsearch use the type "text" for full-text search.

2. Step 2: Match the option with the correct type

   "name": { "type": "text" } correctly uses "text"; others use types for keywords, numbers, or dates.

3. Final Answer:

   "name": { "type": "text" } -> Option A

4. Quick Check:

   Text fields = type "text" [OK]

Hint: Use "text" type for searchable text fields [OK]

Common Mistakes:

• Using "keyword" for full-text search fields
• Assigning numeric or date types to text data
• Missing quotes around field names

3. Given this mapping snippet:

{ "properties": { "age": { "type": "integer" }, "name": { "type": "keyword" } } }

What will happen if you try to search for documents with name containing partial words?

medium

A. Partial word matches will work because keyword fields support full-text search

B. Partial word matches will not work because keyword fields are exact values

C. Elasticsearch will throw a syntax error

D. Partial word matches will work only if age is also searched

Solution

1. Step 1: Understand keyword field behavior

   Keyword fields store exact values and do not support partial or full-text search.

2. Step 2: Analyze the search behavior for partial words

   Since name is keyword type, partial matches will fail; only exact matches work.

3. Final Answer:

   Partial word matches will not work because keyword fields are exact values -> Option B

4. Quick Check:

   Keyword = exact match only [OK]

Hint: Keyword fields do exact matches only, no partial search [OK]

Common Mistakes:

• Assuming keyword fields support partial matching
• Expecting syntax errors from valid mappings
• Confusing integer field with text search behavior

4. You defined this mapping:

{ "properties": { "date": { "type": "text" } } }

What is the problem with this mapping if you want to filter by date range?

medium

A. The field name "date" is reserved and cannot be used

B. There is no problem; text type works for date filtering

C. The type should be "date" to enable date range filtering

D. You must add "index": false to filter by date

Solution

1. Step 1: Identify the correct type for date fields

   Date range filtering requires the field to be of type "date" in Elasticsearch.

2. Step 2: Check the given mapping type

   The mapping uses "text" type, which is not suitable for date operations like range filtering.

3. Final Answer:

   The type should be "date" to enable date range filtering -> Option C

4. Quick Check:

   Date filtering needs type "date" [OK]

Hint: Use type "date" for date range filters [OK]

Common Mistakes:

• Using text type for date fields
• Thinking field names are reserved keywords
• Adding index false disables searching, not filtering

5. You want to store a user's profile with fields: username (exact match), bio (full-text search), and signup_date (date range queries). Which mapping correctly defines these fields?

hard

A. { "properties": { "username": { "type": "keyword" }, "bio": { "type": "text" }, "signup_date": { "type": "date" } } }

B. { "properties": { "username": { "type": "text" }, "bio": { "type": "keyword" }, "signup_date": { "type": "text" } } }

C. { "properties": { "username": { "type": "integer" }, "bio": { "type": "text" }, "signup_date": { "type": "date" } } }

D. { "properties": { "username": { "type": "keyword" }, "bio": { "type": "keyword" }, "signup_date": { "type": "integer" } } }

Solution

1. Step 1: Match each field to its correct type

   Username needs exact matches, so "keyword" is correct. Bio needs full-text search, so "text" is correct. Signup_date needs date range queries, so "date" is correct.

2. Step 2: Verify the options

   { "properties": { "username": { "type": "keyword" }, "bio": { "type": "text" }, "signup_date": { "type": "date" } } } matches all these requirements correctly. Others mix types incorrectly.

3. Final Answer:

   { "properties": { "username": { "type": "keyword" }, "bio": { "type": "text" }, "signup_date": { "type": "date" } } } -> Option A

4. Quick Check:

   Correct types for exact, full-text, and date fields [OK]

Hint: Use keyword for exact, text for full-text, date for dates [OK]

Common Mistakes:

• Mixing keyword and text types incorrectly
• Using integer for date fields
• Confusing full-text and exact match types