Index mappings overview in Elasticsearch - Time & Space Complexity

Time Complexity: Index mappings overview

O(n)

Understanding Time Complexity

When we create index mappings in Elasticsearch, we define how data is stored and searched. Understanding time complexity helps us see how the setup work grows as we add more fields or documents.

We want to know how the time to create or update mappings changes when the index size or field count increases.

Scenario Under Consideration

Analyze the time complexity of this index mapping creation snippet.

PUT /my-index
{
  "mappings": {
    "properties": {
      "name": { "type": "text" },
      "age": { "type": "integer" },
      "email": { "type": "keyword" }
    }
  }
}
    

This code creates an index with three fields and their types defined.

Identify Repeating Operations

Look at what repeats when processing mappings.

• Primary operation: Processing each field's definition in the mapping.
• How many times: Once for each field in the mapping.

How Execution Grows With Input

As you add more fields, the work to process mappings grows.

Input Size (fields)	Approx. Operations
10	10 operations
100	100 operations
1000	1000 operations

Pattern observation: The time grows directly with the number of fields.

Final Time Complexity

Time Complexity: O(n)

This means the time to process mappings grows linearly with the number of fields defined.

Common Mistake

[X] Wrong: "Adding more fields does not affect mapping processing time much."

[OK] Correct: Each field requires separate processing, so more fields mean more work and longer processing time.

Interview Connect

Knowing how mapping size affects processing helps you design efficient indexes and answer questions about scaling Elasticsearch setups confidently.

Self-Check

"What if we added nested fields inside the mapping? How would that change the time complexity?"

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