Why mappings define document structure in Elasticsearch - Quick Recap

Recall & Review

beginner

What is a mapping in Elasticsearch?

A mapping in Elasticsearch is like a blueprint that defines how documents and their fields are stored and indexed. It tells Elasticsearch what type of data each field holds, such as text, number, or date.

beginner

Why do mappings define the document structure in Elasticsearch?

Mappings define document structure because they specify the data types and rules for each field. This helps Elasticsearch understand how to index and search the data efficiently.

intermediate

How does mapping affect searching in Elasticsearch?

Mapping affects searching by determining how fields are analyzed and stored. For example, a text field might be broken into words for full-text search, while a keyword field is stored as is for exact matching.

intermediate

What happens if you don't define a mapping before indexing documents?

If no mapping is defined, Elasticsearch tries to guess the data types automatically. This can lead to incorrect types and inefficient searches, so defining mappings helps avoid surprises.

advanced

Can mappings be changed after documents are indexed?

Mappings are mostly fixed after indexing. You can add new fields, but changing existing field types is not allowed. This is why planning your mappings before indexing is important.

What does a mapping in Elasticsearch primarily define?

A The network settings for Elasticsearch cluster

B The user permissions for documents

C The structure and data types of documents

D The hardware requirements for Elasticsearch

Mappings define how documents are structured and what data types each field has.

If you do not define a mapping, what does Elasticsearch do?

A Automatically guesses field types

B Requires manual input for each document

C Deletes the documents

D Refuses to index documents

Elasticsearch tries to guess the data types automatically if no mapping is provided.

Why is it important to define mappings before indexing?

A To ensure correct data types and efficient searching

B To speed up the network connection

C To reduce disk space usage only

D To enable user authentication

Defining mappings helps Elasticsearch index data correctly and search efficiently.

Which of the following can you NOT do after documents are indexed?

A Index new documents

B Add new fields to the mapping

C Search documents

D Change the data type of an existing field

Changing existing field types after indexing is not allowed in Elasticsearch.

How does mapping affect full-text search?

A It disables full-text search

B It defines how text fields are analyzed and broken into words

C It encrypts the text fields

D It stores text fields as images

Mapping defines how text fields are analyzed, which is essential for full-text search.

Explain why mappings are important for defining document structure in Elasticsearch.

Think about how Elasticsearch knows what kind of data each field holds.

Describe what happens if you index documents without defining a mapping first.

Consider the risks of automatic guessing.

Practice

1. Why do mappings define the structure of documents in Elasticsearch?

easy

A. Because they specify the data types and field properties for each document field

B. Because they store the actual data of the documents

C. Because they control the network settings of Elasticsearch nodes

D. Because they define the user access permissions

Solution

1. Step 1: Understand the role of mappings

   Mappings tell Elasticsearch how to interpret each field in a document, like whether a field is text, number, date, etc.

2. Step 2: Differentiate mappings from other settings

   Mappings do not store data or control network or permissions; they only define the structure and data types.

3. Final Answer:

   Because they specify the data types and field properties for each document field -> Option A

4. Quick Check:

   Mappings = Define document structure [OK]

Hint: Mappings define field types, not data or permissions [OK]

Common Mistakes:

• Thinking mappings store the actual document data
• Confusing mappings with network or security settings
• Assuming mappings are optional for document structure

2. Which of the following is the correct way to define a mapping for a field named age as an integer in Elasticsearch?

easy

A. { "age": { "datatype": "int" } }

B. { "age": "integer" }

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

D. { "age": { "type": "text" } }

Solution

1. Step 1: Check the correct syntax for field type

   Elasticsearch mapping requires the field name with a nested object specifying type and its value, e.g., integer.

2. Step 2: Validate the options

   { "age": { "type": "integer" } } uses correct JSON with type: integer. { "age": "integer" } misses the nested object. { "age": { "datatype": "int" } } uses wrong key datatype. { "age": { "type": "text" } } sets type to text, not integer.

3. Final Answer:

   { "age": { "type": "integer" } } -> Option C

4. Quick Check:

   Correct mapping syntax = { "age": { "type": "integer" } } [OK]

Hint: Use {field: {type: datatype}} format for mappings [OK]

Common Mistakes:

• Using wrong keys like 'datatype' instead of 'type'
• Not nesting the type inside an object
• Confusing 'text' type with 'integer'

3. Given this mapping for a field price as float:

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

What will happen if you index a document with "price": "cheap"?

medium

A. Elasticsearch will store the string 'cheap' as is without error

B. Elasticsearch will index the document but ignore the price field

C. Elasticsearch will convert 'cheap' to 0.0 automatically

D. Elasticsearch will reject the document with a mapping type conflict error

Solution

1. Step 1: Understand type enforcement in mappings

   Elasticsearch enforces the data type defined in mappings. If a field is float, it expects a number.

2. Step 2: Analyze the input value

   The value 'cheap' is a string, not a float, so Elasticsearch will raise a type conflict error when indexing.

3. Final Answer:

   Elasticsearch will reject the document with a mapping type conflict error -> Option D

4. Quick Check:

   Type mismatch causes error = Elasticsearch will reject the document with a mapping type conflict error [OK]

Hint: Data must match mapping type or indexing fails [OK]

Common Mistakes:

• Assuming Elasticsearch auto-converts strings to numbers
• Thinking Elasticsearch silently ignores wrong types
• Believing string values are stored despite float mapping

4. You defined a mapping for a field date as date type, but your documents have dates in the format "dd-MM-yyyy". What is the likely problem and how to fix it?

medium

A. Elasticsearch will parse dates correctly by default; no fix needed

B. Elasticsearch will fail to parse dates; fix by specifying the correct date format in the mapping

C. Elasticsearch will store dates as strings; fix by changing type to text

D. Elasticsearch will ignore the date field; fix by removing the field from documents

Solution

1. Step 1: Recognize default date format

   Elasticsearch expects dates in ISO 8601 format by default, not 'dd-MM-yyyy'.

2. Step 2: Fix by specifying format in mapping

   To parse custom date formats, you must add a format property in the mapping with the correct pattern.

3. Final Answer:

   Elasticsearch will fail to parse dates; fix by specifying the correct date format in the mapping -> Option B

4. Quick Check:

   Date format mismatch = specify format in mapping [OK]

Hint: Set date format in mapping to match document dates [OK]

Common Mistakes:

• Assuming Elasticsearch auto-detects all date formats
• Changing type to text instead of fixing format
• Ignoring parsing errors and expecting correct search

5. You want to optimize search speed on a large text field description. How can defining the mapping help achieve this?

hard

A. By setting the field type to text with a custom analyzer for better indexing

B. By setting the field type to keyword to avoid full-text analysis

C. By omitting the field from the mapping so Elasticsearch guesses the type

D. By setting the field type to integer to speed up searches

Solution

1. Step 1: Understand field types for text search

   Text fields use analyzers to break text into searchable tokens. Custom analyzers can improve search relevance and speed.

2. Step 2: Evaluate options for optimization

   Setting type to text with a custom analyzer helps optimize indexing and searching. keyword is for exact matches, not full-text search. Omitting mapping causes guessing, which is less efficient. Integer type is invalid for text.

3. Final Answer:

   By setting the field type to text with a custom analyzer for better indexing -> Option A

4. Quick Check:

   Custom analyzer on text field = faster, better search [OK]

Hint: Use custom analyzers on text fields for faster search [OK]

Common Mistakes:

• Using keyword type for full-text search
• Not defining mapping and relying on defaults
• Assigning wrong data types like integer to text fields