Metric aggregations (avg, sum, min, max) in Elasticsearch - Time & Space Complexity

Time Complexity: Metric aggregations (avg, sum, min, max)

O(n)

Understanding Time Complexity

When using metric aggregations like average, sum, minimum, and maximum in Elasticsearch, it's important to know how the time to get results changes as data grows.

We want to understand how the work done grows when there are more documents to process.

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

GET /sales/_search
{
  "size": 0,
  "aggs": {
    "average_price": { "avg": { "field": "price" } },
    "total_revenue": { "sum": { "field": "revenue" } },
    "lowest_price": { "min": { "field": "price" } },
    "highest_price": { "max": { "field": "price" } }
  }
}
    

This query calculates average, sum, minimum, and maximum values for fields across all matching documents.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Scanning each document once to read the field values.
• How many times: Once per document in the search results.

How Execution Grows With Input

As the number of documents grows, the time to compute these metrics grows roughly in direct proportion.

Input Size (n)	Approx. Operations
10	10 field reads and updates
100	100 field reads and updates
1000	1000 field reads and updates

Pattern observation: Doubling the number of documents roughly doubles the work done.

Final Time Complexity

Time Complexity: O(n)

This means the time to compute these metrics grows linearly with the number of documents processed.

Common Mistake

[X] Wrong: "Metric aggregations instantly return results regardless of data size."

[OK] Correct: Even though Elasticsearch is fast, it still needs to look at each document's field to calculate metrics, so more data means more work.

Interview Connect

Understanding how metric aggregations scale helps you explain performance considerations clearly, showing you grasp how data size affects query speed.

Self-Check

"What if we added a filter to reduce documents before aggregation? How would the time complexity change?"

Practice

1. What does the avg metric aggregation calculate in an Elasticsearch query?

easy

A. The average value of a numeric field across documents

B. The total count of documents matching the query

C. The maximum value of a numeric field

D. The minimum value of a numeric field

Solution

1. Step 1: Understand the purpose of avg aggregation

   The avg aggregation calculates the average (mean) of values in a numeric field.

2. Step 2: Compare with other metric aggregations

   Other aggregations like sum, min, and max calculate total, minimum, and maximum respectively, not average.

3. Final Answer:

   The average value of a numeric field across documents -> Option A

4. Quick Check:

   avg = average value [OK]

Hint: avg means average value, not count or min/max [OK]

Common Mistakes:

• Confusing avg with sum or count
• Thinking avg returns min or max values
• Mixing avg with document count

2. Which of the following is the correct syntax to calculate the sum of the field price in an Elasticsearch aggregation?

easy

A. "aggs": { "total_price": { "sum": { "field": "price" } } }

B. "aggs": { "total_price": { "avg": { "field": "price" } } }

C. "aggs": { "total_price": { "max": { "field": "price" } } }

D. "aggs": { "total_price": { "min": { "field": "price" } } }

Solution

1. Step 1: Identify the aggregation type for sum

   The aggregation type to calculate sum is sum.

2. Step 2: Check the syntax structure

   The correct syntax uses "sum": { "field": "price" } inside aggs.

3. Final Answer:

   "aggs": { "total_price": { "sum": { "field": "price" } } } -> Option A

4. Quick Check:

   sum aggregation syntax = "aggs": { "total_price": { "sum": { "field": "price" } } } [OK]

Hint: sum uses "sum": { "field": "fieldname" } syntax [OK]

Common Mistakes:

• Using avg or max instead of sum
• Missing the field name inside sum
• Wrong nesting of aggregation keys

3. Given this Elasticsearch aggregation query snippet, what will be the output for the max_price aggregation?

{
  "aggs": {
    "max_price": {
      "max": { "field": "price" }
    }
  }
}

Assuming the documents have prices: 10, 25, 7, 30, 15.

medium

A. 25

B. 30

C. 15

D. 10

Solution

1. Step 1: Understand max aggregation

   The max aggregation returns the highest value of the specified field.

2. Step 2: Identify the maximum price from the list

   From the prices 10, 25, 7, 30, 15, the maximum is 30.

3. Final Answer:

   30 -> Option B

4. Quick Check:

   max price = 30 [OK]

Hint: max returns the highest number in the field values [OK]

Common Mistakes:

• Choosing the second highest value instead of max
• Confusing max with avg or sum
• Ignoring the actual field values

4. Identify the error in this Elasticsearch aggregation query that tries to calculate the minimum value of the field age:

{
  "aggs": {
    "min_age": {
      "min": "age"
    }
  }
}

medium

A. The query is missing a "query" section

B. The aggregation name "min_age" is invalid

C. The aggregation type should be "max" instead of "min"

D. The field name should be inside a nested object with key "field"

Solution

1. Step 1: Check the syntax for min aggregation

   The min aggregation requires the field name inside an object with key "field".

2. Step 2: Identify the error in the given query

   The query uses "min": "age" instead of "min": { "field": "age" } which is incorrect syntax.

3. Final Answer:

   The field name should be inside a nested object with key "field" -> Option D

4. Quick Check:

   min aggregation needs "field": "age" [OK]

Hint: Field must be inside { "field": "name" } for metric aggs [OK]

Common Mistakes:

• Passing field name as string directly without object
• Confusing aggregation type names
• Assuming query section is mandatory for aggregation

5. You want to find the average, sum, minimum, and maximum values of the field score using the avg, sum, min, and max aggregations in a single Elasticsearch query. Which aggregation structure correctly achieves this?

hard

A. { "aggs": { "score_metrics": { "metric": [ { "avg": { "field": "score" } }, { "sum": { "field": "score" } } ] } } }

B. { "aggs": { "score_stats": { "stats": { "field": "score" } } } }

C. { "aggs": { "avg_score": { "avg": { "field": "score" } }, "sum_score": { "sum": { "field": "score" } }, "min_score": { "min": { "field": "score" } }, "max_score": { "max": { "field": "score" } } } }

D. { "aggs": { "score": { "avg": { "field": "score" }, "sum": { "field": "score" }, "min": { "field": "score" }, "max": { "field": "score" } } } }

Solution

1. Step 1: Understand how to combine multiple metric aggregations

   Each metric aggregation must be a separate named aggregation inside aggs.

2. Step 2: Analyze each option's structure

   { "aggs": { "avg_score": { "avg": { "field": "score" } }, "sum_score": { "sum": { "field": "score" } }, "min_score": { "min": { "field": "score" } }, "max_score": { "max": { "field": "score" } } } } correctly defines four separate aggregations for avg, sum, min, and max on the field score. { "aggs": { "score_stats": { "stats": { "field": "score" } } } } uses stats which returns all metrics but is not separate aggregations. { "aggs": { "score_metrics": { "metric": [ { "avg": { "field": "score" } }, { "sum": { "field": "score" } } ] } } } and D have invalid syntax or unsupported structures.

3. Final Answer:

   Separate named aggregations for avg, sum, min, and max inside aggs -> Option C

4. Quick Check:

   Multiple metric aggs need separate keys inside aggs [OK]

Hint: Use separate named aggs for each metric under aggs [OK]

Common Mistakes:

• Trying to combine metrics inside one aggregation object
• Using unsupported array or metric keys
• Confusing stats aggregation with separate metric aggs