Dynamic vs explicit mapping in Elasticsearch

Introduction

Mapping tells Elasticsearch how to understand and store your data. Dynamic mapping guesses the data type automatically, while explicit mapping means you tell Elasticsearch exactly what each field is.

When you want Elasticsearch to automatically add new fields without manual setup.

When you know the exact data types and want to control how data is indexed.

When you want to avoid mistakes from wrong automatic guesses.

When you want to optimize search performance by defining field types clearly.

When you want to prevent unwanted fields from being added to your index.

Syntax

Elasticsearch

PUT /my_index
{
  "mappings": {
    "dynamic": true | false | "strict",
    "properties": {
      "field_name": { "type": "text" | "keyword" | "date" | ... }
    }
  }
}

dynamic can be true (default), false, or strict.

properties defines explicit fields and their types.

Examples

Dynamic mapping is enabled, so new fields are added automatically.

Elasticsearch

PUT /my_index
{
  "mappings": {
    "dynamic": true
  }
}

Dynamic mapping is off. Only name and age fields are allowed.

Elasticsearch

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

Strict mode rejects any new fields not defined explicitly.

Elasticsearch

PUT /my_index
{
  "mappings": {
    "dynamic": "strict",
    "properties": {
      "email": { "type": "keyword" }
    }
  }
}

Sample Program

This creates an index with explicit mapping. The pages field is not defined and dynamic mapping is strict, so it causes an error.

Elasticsearch

PUT /library
{
  "mappings": {
    "dynamic": "strict",
    "properties": {
      "title": { "type": "text" },
      "author": { "type": "keyword" },
      "published_year": { "type": "integer" }
    }
  }
}

POST /library/_doc/1
{
  "title": "Learn Elasticsearch",
  "author": "Jane Doe",
  "published_year": 2023,
  "pages": 250
}

Important Notes

Dynamic mapping is convenient but can cause unexpected fields to be added.

Explicit mapping gives you control and can improve search speed and accuracy.

Use dynamic: strict to prevent any new fields from being added by mistake.

Summary

Dynamic mapping lets Elasticsearch guess field types automatically.

Explicit mapping means you define each field and its type yourself.

Choosing between them depends on how much control and safety you want.

Practice

1. What is the main difference between dynamic mapping and explicit mapping in Elasticsearch?

easy

A. Dynamic mapping automatically detects field types, explicit mapping requires manual definition.

B. Dynamic mapping requires manual field type definition, explicit mapping guesses types automatically.

C. Dynamic mapping disables indexing, explicit mapping enables indexing.

D. Dynamic mapping is only for text fields, explicit mapping is only for numeric fields.

Solution

1. Step 1: Understand dynamic mapping

   Dynamic mapping lets Elasticsearch guess the data type of fields automatically when new data arrives.

2. Step 2: Understand explicit mapping

   Explicit mapping means you define each field's type and settings manually before indexing data.

3. Final Answer:

   Dynamic mapping automatically detects field types, explicit mapping requires manual definition. -> Option A

4. Quick Check:

   Dynamic = auto detect, Explicit = manual define [OK]

Hint: Dynamic guesses types; explicit means you set types yourself [OK]

Common Mistakes:

• Confusing which mapping guesses types
• Thinking dynamic disables indexing
• Assuming explicit mapping is only for numbers

2. Which JSON snippet correctly defines an explicit mapping for a field age as an integer?

easy

A. {"mappings": {"properties": {"age": "number"}}}

B. {"mappings": {"age": {"type": "text"}}}

C. {"properties": {"age": "integer"}}

D. {"mappings": {"properties": {"age": {"type": "integer"}}}}

Solution

1. Step 1: Check correct mapping structure

   Explicit mapping requires "mappings" with "properties" and field name with type inside.

2. Step 2: Verify field type for age

   "age" field must have "type": "integer" to define it as integer.

3. Final Answer:

   {"mappings": {"properties": {"age": {"type": "integer"}}}} -> Option D

4. Quick Check:

   Correct JSON structure with integer type [OK]

Hint: Explicit mapping needs mappings > properties > field > type [OK]

Common Mistakes:

• Missing 'properties' level in JSON
• Using wrong type names like 'number' instead of 'integer'
• Placing fields outside 'mappings'

3. Given this explicit mapping, what will be the type of the price field after indexing?

{"mappings": {"properties": {"price": {"type": "float"}}}}

medium

A. integer

B. text

C. float

D. keyword

Solution

1. Step 1: Read the explicit mapping for price

   The mapping defines "price" with "type": "float", so Elasticsearch will store it as a floating-point number.

2. Step 2: Understand type assignment

   Explicit mapping overrides dynamic guessing, so price will be float regardless of input data.

3. Final Answer:

   float -> Option C

4. Quick Check:

   Explicit float mapping means price = float [OK]

Hint: Explicit mapping sets exact type, here float for price [OK]

Common Mistakes:

• Assuming price becomes integer automatically
• Thinking dynamic mapping applies here
• Confusing float with text or keyword

4. You have this mapping snippet:

{"mappings": {"properties": {"date": {"type": "date"}}}}

After indexing a document with "date": "not-a-date", what error will occur?

medium

A. No error, field stored as text

B. Document rejected with parsing exception

C. Field ignored silently

D. Mapping conflict error due to wrong type

Solution

1. Step 1: Check mapping type for date

   The field "date" is explicitly mapped as "date" type, so Elasticsearch expects a valid date format.

2. Step 2: Indexing invalid date string

   Indexing "not-a-date" will cause a parsing exception because it cannot convert the string to a date.

3. Final Answer:

   Document rejected with parsing exception -> Option B

4. Quick Check:

   Invalid date string causes parsing error [OK]

Hint: Invalid date string causes parsing error, not silent ignore [OK]

Common Mistakes:

• Thinking field stores as text automatically
• Assuming no error occurs
• Believing field is ignored silently

5. You want to prevent Elasticsearch from automatically adding new fields to your index but still allow existing fields to be indexed. Which mapping setting should you use?

hard

A. "dynamic": "strict"

B. "dynamic": "true"

C. "dynamic": "false"

D. "dynamic": "runtime"

Solution

1. Step 1: Understand dynamic mapping options

   "dynamic": "true" allows new fields to be added automatically, "false" ignores new fields, "strict" rejects documents with unknown fields.

2. Step 2: Choose setting to prevent new fields but allow existing

   "strict" rejects documents with new fields, so only existing fields are indexed, preventing unwanted additions.

3. Final Answer:

   "dynamic": "strict" -> Option A

4. Quick Check:

   Use strict to block new fields, allow existing [OK]

Hint: Use dynamic: strict to block new fields but keep existing [OK]

Common Mistakes:

• Using dynamic: false which ignores new fields silently
• Using dynamic: true which allows new fields
• Confusing runtime with dynamic setting