Bucket aggregations (terms, histogram) in Elasticsearch - Step-by-Step Execution

Concept Flow - Bucket aggregations (terms, histogram)

Start Query

↓

Define Aggregation Type

↓

Terms Aggregation

↓

Group by unique terms

↓

Count docs per term

↓

Histogram Aggregation

↓

Define intervals

↓

Group docs by range buckets

↓

Count docs per bucket

↓

Return Aggregation Results

↓

End

The query starts by defining the aggregation type, either terms or histogram, groups documents accordingly, counts documents per bucket, and returns the results.

Execution Sample

Elasticsearch

{
  "aggs": {
    "by_category": {
      "terms": { "field": "category" }
    }
  }
}

This query groups documents by unique 'category' terms and counts how many documents fall into each category.

Execution Table

Step	Aggregation Type	Input Data	Action	Output
1	Terms	Documents with categories: ["books", "books", "toys", "books", "toys"]	Group by unique terms	Buckets: ["books", "toys"]
2	Terms	Buckets: ["books", "toys"]	Count docs per term	{"books": 3, "toys": 2}
3	Histogram	Documents with prices: [5, 12, 17, 22, 27]	Define interval size 10	Buckets: [0-9], [10-19], [20-29]
4	Histogram	Buckets: [0-9], [10-19], [20-29]	Group docs by price range	{"0-9": 1, "10-19": 2, "20-29": 2}
5	End	-	Return aggregation results	Aggregation response with buckets and counts

💡 All documents processed and buckets counted, aggregation complete.

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4	Final
Buckets (Terms)	empty	["books", "toys"]	{"books": 3, "toys": 2}	-	-	{"books": 3, "toys": 2}
Buckets (Histogram)	empty	-	-	[0-9], [10-19], [20-29]	{"0-9": 1, "10-19": 2, "20-29": 2}	{"0-9": 1, "10-19": 2, "20-29": 2}

Key Moments - 3 Insights

Why do terms aggregation buckets only show unique terms?

Because terms aggregation groups documents by unique values of the specified field, as shown in execution_table step 1 where unique terms 'books' and 'toys' form buckets.

How does histogram aggregation decide bucket ranges?

Histogram aggregation uses the defined interval size to create numeric ranges, as in step 3 where interval 10 creates buckets [0-9], [10-19], [20-29].

Why do buckets have counts instead of document lists?

Aggregations count documents per bucket for efficiency; the counts summarize how many documents fall into each bucket, shown in steps 2 and 4.

Visual Quiz - 3 Questions

Look at the execution_table, what is the count for the 'books' bucket after step 2?

A 3

B 2

C 5

D 1

💡 Hint

Check execution_table row with Step 2 under Output column.

At which step does the histogram aggregation define its bucket intervals?

A Step 1

B Step 3

C Step 4

D Step 2

💡 Hint

Look for the step mentioning interval size in execution_table.

If the interval size in histogram aggregation changed from 10 to 5, how would the buckets change?

A Buckets would be larger ranges

B Buckets would stay the same

C Buckets would be smaller ranges, more buckets

D Buckets would disappear

💡 Hint

Refer to variable_tracker for how intervals define bucket ranges.

Concept Snapshot

Bucket Aggregations in Elasticsearch:
- Terms aggregation groups documents by unique field values.
- Histogram aggregation groups numeric values into fixed intervals.
- Each bucket counts documents matching its criteria.
- Results show buckets with doc counts for analysis.
- Useful for grouping and summarizing data quickly.

Full Transcript

This visual execution trace shows how Elasticsearch bucket aggregations work. The process starts by defining the aggregation type: terms or histogram. Terms aggregation groups documents by unique values of a field, creating buckets for each unique term and counting documents in each bucket. Histogram aggregation groups numeric values into fixed-size intervals, creating buckets for ranges and counting documents per range. The execution table traces these steps with example data, showing bucket creation and document counts. The variable tracker shows how bucket contents evolve after each step. Key moments clarify common confusions about bucket uniqueness, interval definition, and why counts are used. The quiz tests understanding of bucket counts, interval steps, and effects of changing interval size. The snapshot summarizes the core ideas for quick reference.

Practice

1.

What does the terms aggregation do in Elasticsearch?

easy

A. Sorts documents by date in ascending order

B. Groups documents by unique values of a field and counts them

C. Filters documents based on a numeric range

D. Calculates the average value of a numeric field

Solution

1. Step 1: Understand the purpose of terms aggregation

   The terms aggregation groups documents by unique values of a specified field.

2. Step 2: Recognize the output of terms aggregation

   It counts how many documents fall into each unique value group.

3. Final Answer:

   Groups documents by unique values of a field and counts them -> Option B

4. Quick Check:

   terms aggregation = grouping by unique values [OK]

Hint: Remember: terms = group by unique values and count [OK]

Common Mistakes:

• Confusing terms with filtering
• Thinking terms sorts documents
• Mixing terms with metric aggregations

2.

Which of the following is the correct syntax for a histogram aggregation on a field named price with interval 50?

{
  "aggs": {
    "price_ranges": {
      "histogram": {
        "field": "price",
        "interval": 50
      }
    }
  }
}

easy

A. Correct as shown

B. Use "interval": "50" (string instead of number)

C. Use "terms" instead of "histogram"

D. Place "interval" outside "histogram" block

Solution

1. Step 1: Check the structure of histogram aggregation

   The histogram aggregation requires a field and a numeric interval inside its block.

2. Step 2: Verify the given JSON syntax

   The example correctly places field and interval inside the histogram object with interval as a number.

3. Final Answer:

   Correct as shown -> Option A

4. Quick Check:

   Histogram syntax with numeric interval = correct [OK]

Hint: Interval must be a number inside histogram block [OK]

Common Mistakes:

• Using string instead of number for interval
• Confusing terms and histogram aggregations
• Placing interval outside histogram object

3.

Given this aggregation query:

{
  "aggs": {
    "by_category": {
      "terms": { "field": "category.keyword" }
    }
  }
}

What will the aggregation return?

medium

A. The average value of the category field

B. A histogram of categories grouped by numeric ranges

C. A list of unique categories with document counts for each

D. A filtered list of documents matching category.keyword

Solution

1. Step 1: Identify the aggregation type and field

   The query uses a terms aggregation on the category.keyword field, which groups by unique values.

2. Step 2: Understand the output of terms aggregation

   It returns buckets for each unique category with counts of documents in each bucket.

3. Final Answer:

   A list of unique categories with document counts for each -> Option C

4. Quick Check:

   Terms aggregation output = unique value buckets with counts [OK]

Hint: Terms aggregation returns unique values with counts [OK]

Common Mistakes:

• Thinking histogram groups string fields
• Expecting average instead of counts
• Confusing filtering with aggregation

4.

Identify the error in this aggregation query:

{
  "aggs": {
    "price_buckets": {
      "histogram": {
        "field": "price",
        "interval": "100"
      }
    }
  }
}

medium

A. The field name "price" is invalid

B. Missing "size" parameter for histogram

C. Histogram aggregation cannot be nested inside aggs

D. The interval value should be a number, not a string

Solution

1. Step 1: Check the type of the interval parameter

   The interval must be a numeric value, but here it is given as a string "100".

2. Step 2: Understand impact of wrong interval type

   Using a string instead of a number causes a syntax error or unexpected behavior in Elasticsearch.

3. Final Answer:

   The interval value should be a number, not a string -> Option D

4. Quick Check:

   Interval must be numeric, not string [OK]

Hint: Interval must be numeric, not quoted string [OK]

Common Mistakes:

• Using string instead of number for interval
• Assuming field name is wrong without checking
• Thinking histogram can't be inside aggs

5.

You want to group sales data by price ranges of 100 units and then within each price range, group by product category. Which aggregation structure should you use?

hard

A. { "aggs": { "price_ranges": { "histogram": { "field": "price", "interval": 100 }, "aggs": { "by_category": { "terms": { "field": "category.keyword" } } } } } }

B. { "aggs": { "by_category": { "terms": { "field": "category.keyword" }, "aggs": { "price_ranges": { "histogram": { "field": "price", "interval": 100 } } } } } }

C. { "aggs": { "price_ranges": { "terms": { "field": "price" }, "aggs": { "by_category": { "histogram": { "field": "category.keyword", "interval": 100 } } } } } }

D. { "aggs": { "by_category": { "histogram": { "field": "category.keyword", "interval": 100 }, "aggs": { "price_ranges": { "terms": { "field": "price" } } } } } }

Solution

1. Step 1: Identify the primary grouping by price ranges

   The outer aggregation should be a histogram on the price field with interval 100 to group sales by price ranges.

2. Step 2: Nest the category grouping inside each price range bucket

   Inside each price range bucket, use a terms aggregation on category.keyword to group by product category.

3. Final Answer:

   Aggregation with histogram on price and nested terms on category -> Option A

4. Quick Check:

   Histogram outer, terms nested = correct structure [OK]

Hint: Nest terms inside histogram for grouped sub-buckets [OK]

Common Mistakes:

• Reversing the order of aggregations
• Using terms for numeric price instead of histogram
• Using histogram on keyword fields