Bird
Raised Fist0
Elasticsearchquery~30 mins

Nested aggregations in Elasticsearch - Mini Project: Build & Apply

Choose your learning style10 modes available
Nested aggregations
📖 Scenario: You work for a bookstore that wants to analyze sales data stored in Elasticsearch. The data includes books with their genres and sales numbers. You want to find out the total sales per genre and also the average sales per book within each genre.
🎯 Goal: Build an Elasticsearch query using nested aggregations to calculate total sales per genre and average sales per book within each genre.
📋 What You'll Learn
Create a terms aggregation on the genre field named genres
Inside genres, create a sum aggregation on the sales field named total_sales
Inside genres, create an average aggregation on the sales field named avg_sales_per_book
Output the complete JSON query with nested aggregations
💡 Why This Matters
🌍 Real World
Nested aggregations help businesses analyze grouped data with multiple metrics in Elasticsearch, such as sales by category with totals and averages.
💼 Career
Understanding nested aggregations is important for roles like data analyst, backend developer, or Elasticsearch engineer working with search and analytics.
Progress0 / 4 steps
1
Create the base aggregation by genre
Create an Elasticsearch aggregation named genres using terms on the field genre.
Elasticsearch
Hint

Use terms aggregation on genre inside aggs.

2
Add total sales sum aggregation inside genres
Inside the genres aggregation, add a sum aggregation named total_sales on the field sales.
Elasticsearch
Hint

Inside genres, add aggs with total_sales sum aggregation on sales.

3
Add average sales per book aggregation inside genres
Inside the genres aggregation, add an avg aggregation named avg_sales_per_book on the field sales alongside total_sales.
Elasticsearch
Hint

Add avg_sales_per_book average aggregation on sales inside genres alongside total_sales.

4
Output the complete nested aggregation query
Print the complete Elasticsearch query JSON with nested aggregations for genres, total_sales, and avg_sales_per_book.
Elasticsearch
Hint

Use print() to output the full JSON query object.

Practice

(1/5)
1. What is the main purpose of nested aggregations in Elasticsearch?
easy
A. To sort documents by a single field
B. To group data inside other groups for multi-level analysis
C. To filter documents based on a condition
D. To update documents in bulk

Solution

  1. Step 1: Recall aggregation basics

    Aggregations group data to summarize or analyze it.
  2. Step 2: Examine nested aggregations

    Nested aggregations group data inside other groups for detailed multi-level insights.
  3. Final Answer:

    To group data inside other groups for multi-level analysis -> Option B
  4. Quick Check:

    Nested aggregations = multi-level grouping [OK]
Hint: Nested aggs always use 'aggs' inside another aggregation [OK]
Common Mistakes:
  • Confusing nested aggregations with filters
  • Thinking nested aggregations sort data
  • Assuming nested aggregations update documents
2. Which of the following is the correct syntax to add a nested aggregation inside a terms aggregation in Elasticsearch?
easy
A. "aggs": { "country": { "terms": { "field": "country" }, "aggs": { "city": { "terms": { "field": "city" } } } } }
B. "nested": { "aggs": { "terms": { "field": "city" } } }
C. "aggs": { "nested_agg": { "terms": { "field": "city" } } }
D. "aggs": { "terms": { "field": "city" }, "aggs": { "nested_agg": { "terms": { "field": "country" } } } }

Solution

  1. Step 1: Identify correct nested aggregation structure

    Nested aggregations are placed inside the "aggs" key of a parent aggregation.
  2. Step 2: Check "aggs": { "country": { "terms": { "field": "country" }, "aggs": { "city": { "terms": { "field": "city" } } } } } structure

    "aggs": { "country": { "terms": { "field": "country" }, "aggs": { "city": { "terms": { "field": "city" } } } } } shows a terms aggregation on "country" with a nested terms aggregation on "city" inside its "aggs" key, which is correct syntax.
  3. Final Answer:

    "aggs": { "country": { "terms": { "field": "country" }, "aggs": { "city": { "terms": { "field": "city" } } } } } -> Option A
  4. Quick Check:

    Nested aggs inside parent's "aggs" key = "aggs": { "country": { "terms": { "field": "country" }, "aggs": { "city": { "terms": { "field": "city" } } } } } [OK]
Hint: Nested aggs go inside parent's "aggs" key, not outside [OK]
Common Mistakes:
  • Placing multiple "aggs" keys at the same level
  • Using "nested" keyword incorrectly
  • Missing the "aggs" key inside parent aggregation
3. Given this Elasticsearch aggregation query snippet:
{
  "aggs": {
    "by_country": {
      "terms": { "field": "country" },
      "aggs": {
        "by_city": {
          "terms": { "field": "city" }
        }
      }
    }
  }
}

What does the nested aggregation by_city do?
medium
A. Groups documents by city inside each country group
B. Filters documents only from one city
C. Sorts countries by city name
D. Counts total documents ignoring country

Solution

  1. Step 1: Analyze the outer aggregation

    "by_country" groups documents by the "country" field.
  2. Step 2: Analyze the nested aggregation

    Inside each country group, "by_city" groups documents by the "city" field.
  3. Final Answer:

    Groups documents by city inside each country group -> Option A
  4. Quick Check:

    Nested terms aggregation groups inside parent group [OK]
Hint: Nested terms aggs group data inside parent buckets [OK]
Common Mistakes:
  • Thinking nested aggs filter data
  • Assuming nested aggs sort data
  • Ignoring the parent aggregation grouping
4. Identify the error in this nested aggregation query:
{
  "aggs": {
    "countries": {
      "terms": { "field": "country" },
      "terms": {
        "field": "city"
      }
    }
  }
}
medium
A. Using "terms" twice at the same level is correct
B. Aggregation names cannot be plural
C. Field names "country" and "city" must be the same
D. Missing nested "aggs" key for the city aggregation

Solution

  1. Step 1: Check aggregation structure

    Each aggregation can have only one aggregation type key like "terms" at its level.
  2. Step 2: Identify nested aggregation placement

    Nested aggregations must be inside an "aggs" key, but here "terms" is repeated instead of nesting inside "aggs".
  3. Final Answer:

    Missing nested "aggs" key for the city aggregation -> Option D
  4. Quick Check:

    Nested aggs require "aggs" key inside parent [OK]
Hint: Nested aggs must be inside "aggs", not repeated aggregation keys [OK]
Common Mistakes:
  • Repeating aggregation type keys at same level
  • Not nesting inside "aggs" key
  • Confusing aggregation names with field names
5. You want to analyze sales data by region, then by product category, and finally by brand using nested aggregations. Which of the following query structures correctly implements this three-level nested aggregation?
hard
A. { "aggs": { "region": { "terms": { "field": "region" }, "terms": { "field": "category" }, "terms": { "field": "brand" } } } }
B. { "aggs": { "region": { "terms": { "field": "region" } }, "category": { "terms": { "field": "category" } }, "brand": { "terms": { "field": "brand" } } } }
C. { "aggs": { "region": { "terms": { "field": "region" }, "aggs": { "category": { "terms": { "field": "category" }, "aggs": { "brand": { "terms": { "field": "brand" } } } } } } } }
D. { "aggs": { "brand": { "terms": { "field": "brand" }, "aggs": { "category": { "terms": { "field": "category" }, "aggs": { "region": { "terms": { "field": "region" } } } } } } } }

Solution

  1. Step 1: Identify the required nesting order

    We want to group first by region, then inside each region by category, then inside each category by brand.
  2. Step 2: Check each option's structure

    { "aggs": { "region": { "terms": { "field": "region" }, "aggs": { "category": { "terms": { "field": "category" }, "aggs": { "brand": { "terms": { "field": "brand" } } } } } } } correctly nests "category" inside "region"'s "aggs", and "brand" inside "category"'s "aggs". Others either flatten or reverse order.
  3. Final Answer:

    { "aggs": { "region": { "terms": { "field": "region" }, "aggs": { "category": { "terms": { "field": "category" }, "aggs": { "brand": { "terms": { "field": "brand" } } } } } } } -> Option C
  4. Quick Check:

    Nested aggs inside parent's "aggs" in correct order = { "aggs": { "region": { "terms": { "field": "region" }, "aggs": { "category": { "terms": { "field": "category" }, "aggs": { "brand": { "terms": { "field": "brand" } } } } } } } [OK]
Hint: Nest each level inside previous level's "aggs" key [OK]
Common Mistakes:
  • Placing all aggregations at top level without nesting
  • Repeating aggregation keys at same level
  • Reversing the desired grouping order
Recommended

Ready to prove it?

Pass the test and this pattern moves unknown strong while earning +1 Grip toward your certificate.

10 questions~5 mineasy hard