Why indexes organize data in Elasticsearch - Performance Analysis

Time Complexity: Why indexes organize data

O(log n)

Understanding Time Complexity

Indexes in Elasticsearch help organize data to make searching faster.

We want to know how the time to find data changes as the amount of data grows.

Scenario Under Consideration

Analyze the time complexity of searching data using an index.

GET /my_index/_search
{
  "query": {
    "match": {
      "title": "elasticsearch"
    }
  }
}
    

This code searches the "title" field in the "my_index" index for the word "elasticsearch".

Identify Repeating Operations

When searching, Elasticsearch looks through the index structure.

• Primary operation: Traversing the index tree to find matching documents.
• How many times: The search moves down the tree levels, which depends on the index size.

How Execution Grows With Input

As the number of documents grows, the index tree grows in height slowly.

Input Size (n)	Approx. Operations
10	About 3 steps down the tree
100	About 7 steps down the tree
1000	About 10 steps down the tree

Pattern observation: The steps grow slowly compared to the number of documents, making search efficient.

Final Time Complexity

Time Complexity: O(log n)

This means the search time grows slowly as data grows, because the index helps find data quickly.

Common Mistake

[X] Wrong: "Searching an index checks every document one by one."

[OK] Correct: The index organizes data so Elasticsearch jumps directly to relevant parts, not checking all documents.

Interview Connect

Understanding how indexes speed up search shows you know how data organization affects performance, a key skill in many programming tasks.

Self-Check

"What if the index was not used and Elasticsearch searched all documents directly? How would the time complexity change?"

Practice

1. Why do Elasticsearch indexes organize data?

easy

A. To slow down data retrieval

B. To store data in random order

C. To make searching fast and efficient

D. To delete data automatically

Solution

1. Step 1: Understand the purpose of indexes

   Indexes are designed to arrange data so that searching can be done quickly and easily.

2. Step 2: Compare options with the purpose

   Only To make searching fast and efficient matches the purpose of indexes; others describe incorrect behaviors.

3. Final Answer:

   To make searching fast and efficient -> Option C

4. Quick Check:

   Indexes speed up search = A [OK]

Hint: Indexes speed up search by organizing data [OK]

Common Mistakes:

• Thinking indexes slow down search
• Believing indexes store data randomly
• Assuming indexes delete data automatically

2. Which of the following is the correct way to create an index in Elasticsearch?

easy

A. PUT /my_index

B. GET /my_index

C. DELETE /my_index

D. POST /my_index/_search

Solution

1. Step 1: Identify the HTTP method for creating an index

   Creating an index uses the PUT method with the index name.

2. Step 2: Match the correct syntax

   PUT /my_index is the correct syntax; others perform different actions.

3. Final Answer:

   PUT /my_index -> Option A

4. Quick Check:

   PUT creates index = D [OK]

Hint: Use PUT to create an index in Elasticsearch [OK]

Common Mistakes:

• Using GET to create an index
• Confusing DELETE with creation
• Using POST for index creation instead of search

3. Given this Elasticsearch query on an index, what does it do?

{"query": {"match": {"title": "Elasticsearch"}}}

medium

A. Updates documents with title 'Elasticsearch'

B. Finds documents where the title contains 'Elasticsearch'

C. Deletes documents with title 'Elasticsearch'

D. Creates a new document with title 'Elasticsearch'

Solution

1. Step 1: Understand the query type

   The query uses 'match' which searches for documents matching the given text in the specified field.

2. Step 2: Interpret the query action

   This query finds documents where the 'title' field contains the word 'Elasticsearch'.

3. Final Answer:

   Finds documents where the title contains 'Elasticsearch' -> Option B

4. Quick Check:

   Match query searches text = C [OK]

Hint: Match queries find documents containing the text [OK]

Common Mistakes:

• Thinking match deletes or updates documents
• Confusing match with document creation
• Assuming match returns all documents

4. You tried to create an index with this command:

POST /my_index

Why might this cause an error?

medium

A. The command should be GET instead

B. The index name is missing

C. POST is only for searching

D. POST is not used to create indexes; PUT is required

Solution

1. Step 1: Recall correct HTTP method for index creation

   Creating an index requires the PUT method, not POST.

2. Step 2: Analyze the command used

   Using POST /my_index tries to create but is invalid syntax, causing an error.

3. Final Answer:

   POST is not used to create indexes; PUT is required -> Option D

4. Quick Check:

   PUT creates index, POST does not = A [OK]

Hint: Use PUT, not POST, to create indexes [OK]

Common Mistakes:

• Using POST instead of PUT for index creation
• Thinking POST is for creating indexes
• Confusing GET with creation commands

5. You want to speed up searches on a text field by controlling how data is saved. Which Elasticsearch feature helps organize data for this purpose?

hard

A. Mappings to define field types and analyzers

B. Deleting old indexes regularly

C. Using GET requests to fetch data

D. Adding more shards without mappings

Solution

1. Step 1: Understand how data organization affects search speed

   Settings and mappings control how data is stored and indexed, affecting search performance.

2. Step 2: Identify the feature that controls field types and analyzers

   Mappings define field types and analyzers, organizing data for efficient searching.

3. Final Answer:

   Mappings to define field types and analyzers -> Option A

4. Quick Check:

   Mappings organize data for fast search = B [OK]

Hint: Use mappings to organize data for faster search [OK]

Common Mistakes:

• Thinking deleting indexes speeds up search
• Confusing GET requests with data organization
• Believing shards alone improve search without mappings