Why aggregations summarize data in Elasticsearch - Performance Analysis

Time Complexity: Why aggregations summarize data

O(n)

Understanding Time Complexity

When using aggregations in Elasticsearch, it is important to understand how the time to summarize data changes as the data grows.

We want to know how the work done by aggregations increases when there are more documents to process.

Scenario Under Consideration

Analyze the time complexity of the following aggregation query.

GET /sales/_search
{
  "size": 0,
  "aggs": {
    "total_revenue": {
      "sum": { "field": "price" }
    }
  }
}
    

This query calculates the total sum of the "price" field across all sales documents.

Identify Repeating Operations

Look at what repeats as the data size grows.

• Primary operation: Summing the "price" field for each document.
• How many times: Once for every document in the index.

How Execution Grows With Input

As the number of documents increases, the aggregation must add more values.

Input Size (n)	Approx. Operations
10	10 sums
100	100 sums
1000	1000 sums

Pattern observation: The work grows directly with the number of documents.

Final Time Complexity

Time Complexity: O(n)

This means the time to compute the sum grows in a straight line as the number of documents increases.

Common Mistake

[X] Wrong: "Aggregations always run instantly no matter how much data there is."

[OK] Correct: Aggregations must look at each document to summarize data, so more documents mean more work and more time.

Interview Connect

Understanding how aggregations scale helps you explain how search engines handle large data efficiently and why performance matters.

Self-Check

What if we changed the aggregation from a sum to a terms aggregation grouping by a field? How would the time complexity change?

Practice

1. What is the main purpose of aggregations in Elasticsearch?

easy

A. To delete documents from the index

B. To summarize data like totals, averages, and counts

C. To update the mapping of fields

D. To create new indexes

Solution

1. Step 1: Understand what aggregations do

   Aggregations are used to get summaries such as totals, averages, and counts from data.

2. Step 2: Compare with other options

   Deleting documents, updating mappings, and creating indexes are not related to summarizing data.

3. Final Answer:

   To summarize data like totals, averages, and counts -> Option B

4. Quick Check:

   Aggregations summarize data = A [OK]

Hint: Aggregations summarize data, not modify it [OK]

Common Mistakes:

• Confusing aggregations with data deletion
• Thinking aggregations change index structure
• Mixing aggregations with indexing operations

2. Which part of an Elasticsearch query contains aggregations?

easy

A. aggs

B. query

C. filter

D. sort

Solution

1. Step 1: Identify the query structure

   Elasticsearch queries have different parts like query, aggs, filter, and sort.

2. Step 2: Locate where aggregations go

   Aggregations are always written inside the aggs section to summarize data.

3. Final Answer:

   aggs -> Option A

4. Quick Check:

   Aggregations inside aggs = A [OK]

Hint: Aggregations live inside the aggs section [OK]

Common Mistakes:

• Putting aggregations inside query or filter
• Confusing aggs with sort
• Missing the aggs keyword

3. Given this aggregation query snippet, what does it calculate?

{"aggs": {"total_sales": {"sum": {"field": "price"}}}}

medium

A. Sums all values in the price field

B. Calculates the average price

C. Finds the maximum price

D. Counts the number of documents

Solution

1. Step 1: Read the aggregation type

   The aggregation uses sum on the field price.

2. Step 2: Understand what sum does

   Sum adds all values in the specified field across documents.

3. Final Answer:

   Sums all values in the price field -> Option A

4. Quick Check:

   sum aggregation = D [OK]

Hint: Sum adds all values in a field [OK]

Common Mistakes:

• Confusing sum with count or average
• Thinking sum finds max value
• Ignoring the field name

4. This aggregation query returns an error. What is the mistake?

{"aggs": {"avg_price": {"average": {"field": "price"}}}}

medium

A. The aggs keyword is misspelled

B. The field name 'price' is invalid

C. Aggregations cannot use numeric fields

D. The aggregation type should be 'avg', not 'average'

Solution

1. Step 1: Check aggregation type spelling

   The correct aggregation for average is avg, not average.

2. Step 2: Validate other parts

   The field name and aggs keyword are correct, and numeric fields are allowed.

3. Final Answer:

   The aggregation type should be 'avg', not 'average' -> Option D

4. Quick Check:

   Use 'avg' for average aggregation = C [OK]

Hint: Use 'avg' keyword, not 'average' [OK]

Common Mistakes:

• Using 'average' instead of 'avg'
• Assuming field name causes error
• Thinking aggs is misspelled

5. You want to find the average price of products but only for those with stock greater than 10. Which aggregation setup is correct?

hard

A. {"aggs": {"avg_price": {"avg": {"field": "price", "gt": 10}}}}

B. {"query": {"term": {"stock": 10}}, "aggs": {"avg_price": {"avg": {"field": "price"}}}}

C. {"query": {"range": {"stock": {"gt": 10}}}, "aggs": {"avg_price": {"avg": {"field": "price"}}}}

D. {"aggs": {"avg_price": {"avg": {"field": "price"}}}, "filter": {"range": {"stock": {"gt": 10}}}}

Solution

1. Step 1: Understand filtering before aggregation

   To filter documents before aggregation, use a query with a range filter on stock > 10.

2. Step 2: Check aggregation syntax

   The aggregation should be inside aggs with avg on the price field.

3. Step 3: Evaluate options

   {"query": {"range": {"stock": {"gt": 10}}}, "aggs": {"avg_price": {"avg": {"field": "price"}}}} correctly filters with query and then aggregates. {"aggs": {"avg_price": {"avg": {"field": "price", "gt": 10}}}} wrongly puts filter inside aggregation. {"query": {"term": {"stock": 10}}, "aggs": {"avg_price": {"avg": {"field": "price"}}}} filters exact stock=10, not greater. {"aggs": {"avg_price": {"avg": {"field": "price"}}}, "filter": {"range": {"stock": {"gt": 10}}}} misplaces filter outside query.

4. Final Answer:

   {"query": {"range": {"stock": {"gt": 10}}}, "aggs": {"avg_price": {"avg": {"field": "price"}}}} -> Option C

5. Quick Check:

   Filter in query, aggregation in aggs = B [OK]

Hint: Filter in query, aggregate in aggs section [OK]

Common Mistakes:

• Putting filters inside aggregation incorrectly
• Using term filter instead of range for greater than
• Placing filter outside query block