Dynamic vs explicit mapping in Elasticsearch - Quick Revision & Key Differences

Recall & Review

beginner

What is dynamic mapping in Elasticsearch?

Dynamic mapping automatically detects and adds new fields to the index mapping when new data arrives without needing manual configuration.

beginner

What does explicit mapping mean in Elasticsearch?

Explicit mapping means you manually define the structure and data types of fields in an index before adding data, giving you full control over how data is stored and searched.

intermediate

What is a key advantage of using explicit mapping?

Explicit mapping helps avoid unexpected data types and ensures consistent search behavior by defining exactly how each field should be indexed.

beginner

How does dynamic mapping handle new fields in incoming documents?

Dynamic mapping automatically adds new fields to the index with inferred data types based on the incoming document's content.

intermediate

What is a potential risk of relying solely on dynamic mapping?

Relying only on dynamic mapping can lead to inconsistent data types, unexpected field mappings, and inefficient searches if data varies or changes over time.

Which mapping type requires you to define field types before indexing data?

A Dynamic mapping

B Explicit mapping

C Automatic mapping

D Default mapping

Explicit mapping means you manually define field types before adding data.

What happens when Elasticsearch receives a new field not in the mapping and dynamic mapping is enabled?

A It ignores the new field

B It throws an error

C It automatically adds the new field with inferred type

D It deletes the document

Dynamic mapping automatically adds new fields with inferred types.

Which is a benefit of explicit mapping over dynamic mapping?

A More control over field types and search behavior

B Faster indexing without configuration

C Automatic detection of new fields

D No need to define any mapping

Explicit mapping gives you control over field types and how data is indexed.

If you want to prevent Elasticsearch from adding new fields automatically, what should you do?

A Delete the index

B Enable dynamic mapping

C Use default mapping

D Disable dynamic mapping or use explicit mapping

Disabling dynamic mapping or using explicit mapping stops automatic addition of new fields.

What is a common problem when using only dynamic mapping in production?

A Field types may be inconsistent causing search issues

B Mapping is too strict

C Data is never indexed

D Elasticsearch crashes

Dynamic mapping can cause inconsistent field types leading to search problems.

Explain the difference between dynamic and explicit mapping in Elasticsearch.

Think about how new fields are handled when data is added.

What are the advantages and risks of using dynamic mapping?

Consider what happens when new or unexpected data arrives.

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