$bucket and $bucketAuto for distribution in MongoDB

Introduction

These operators help group data into ranges or buckets to see how values are spread out.

You want to see how many sales fall into different price ranges.

You want to group ages of people into age groups like 0-20, 21-40, etc.

You want to divide test scores into equal groups to compare performance.

You want to summarize data by ranges instead of exact values.

Syntax

MongoDB

db.collection.aggregate([
  {
    $bucket: {
      groupBy: <expression>,
      boundaries: [<lower1>, <lower2>, ..., <upper>],
      default: <optional-default-bucket>,
      output: { <field1>: { <accumulator1> }, ... }
    }
  }
])

// or

db.collection.aggregate([
  {
    $bucketAuto: {
      groupBy: <expression>,
      buckets: <number-of-buckets>,
      output: { <field1>: { <accumulator1> }, ... }
    }
  }
])

$bucket requires you to specify exact boundaries for the groups.

$bucketAuto automatically creates buckets with roughly equal numbers of documents.

Examples

This groups sales by price ranges: 0-99, 100-199, 200-299, and others.

MongoDB

db.sales.aggregate([
  {
    $bucket: {
      groupBy: "$price",
      boundaries: [0, 100, 200, 300],
      default: "Other",
      output: { count: { $sum: 1 } }
    }
  }
])

This automatically divides sales into 3 buckets with about equal counts.

MongoDB

db.sales.aggregate([
  {
    $bucketAuto: {
      groupBy: "$price",
      buckets: 3,
      output: { count: { $sum: 1 } }
    }
  }
])

Sample Program

This groups products by quantity in stock into ranges 0-49, 50-99, 100-149, 150+.

MongoDB

db.products.aggregate([
  {
    $bucket: {
      groupBy: "$quantity",
      boundaries: [0, 50, 100, 150],
      default: "Other",
      output: { count: { $sum: 1 } }
    }
  }
])

Important Notes

Use $bucket when you know the exact ranges you want.

Use $bucketAuto when you want MongoDB to decide ranges for balanced groups.

The default bucket catches values less than the first boundary or invalid values in $bucket.

Summary

$bucket groups data by fixed ranges you define.

$bucketAuto groups data into balanced buckets automatically.

Both help understand how data is spread across ranges.

Practice

1. What is the main difference between $bucket and $bucketAuto in MongoDB aggregation?

easy

A. $bucket requires you to specify boundaries; $bucketAuto creates balanced buckets automatically.

B. $bucket automatically balances buckets; $bucketAuto requires manual boundaries.

C. $bucket groups by exact values; $bucketAuto groups by string length.

D. $bucket is used only for numeric data; $bucketAuto only for dates.

Solution

1. Step 1: Understand $bucket behavior

   $bucket requires explicit boundaries to group documents into fixed ranges.

2. Step 2: Understand $bucketAuto behavior

   $bucketAuto automatically calculates boundaries to create balanced buckets based on data distribution.

3. Final Answer:

   $bucket requires you to specify boundaries; $bucketAuto creates balanced buckets automatically. -> Option A

4. Quick Check:

   $bucket vs $bucketAuto = C [OK]

Hint: Remember: manual ranges for $bucket, auto ranges for $bucketAuto [OK]

Common Mistakes:

• Confusing which operator auto-calculates boundaries
• Thinking $bucketAuto needs manual boundaries
• Assuming $bucket works only with strings

2. Which of the following is the correct syntax to use $bucket in a MongoDB aggregation pipeline?

easy

A. { $bucket: { groupBy: "$score", ranges: [0, 50, 100], default: "Other" } }

B. { $bucket: { field: "$score", ranges: [0, 50, 100] } }

C. { $bucketAuto: { groupBy: "$score", buckets: 3 } }

D. { $bucket: { groupBy: "$score", boundaries: [0, 50, 100] } }

Solution

1. Step 1: Check required fields for $bucket

   $bucket requires groupBy and boundaries. The default field is optional.

2. Step 2: Identify correct syntax

   { $bucket: { groupBy: "$score", boundaries: [0, 50, 100] } } correctly uses groupBy and boundaries without unnecessary fields.

3. Final Answer:

   { $bucket: { groupBy: "$score", boundaries: [0, 50, 100] } } -> Option D

4. Quick Check:

   Correct $bucket syntax = D [OK]

Hint: Remember: groupBy and boundaries are mandatory for $bucket [OK]

Common Mistakes:

• Using field instead of groupBy
• Confusing $bucket with $bucketAuto syntax
• Omitting required boundaries array

3. Given the collection documents: [{score: 10}, {score: 20}, {score: 55}, {score: 70}, {score: 90}], what will be the output buckets using this aggregation?

{ $bucket: { groupBy: "$score", boundaries: [0, 50, 100], default: "Other", output: { count: { $sum: 1 } } } }

medium

A. [{_id: 0, count: 2}, {_id: 50, count: 2}, {_id: "Other", count: 1}]

B. [{_id: 0, count: 3}, {_id: 50, count: 2}]

C. [{_id: 0, count: 2}, {_id: 50, count: 3}]

D. [{_id: 0, count: 5}]

Solution

1. Step 1: Assign documents to buckets by boundaries

   Boundaries are [0, 50, 100]. Scores 10, 20 fall into bucket 0-50 (count 2). Scores 55, 70, 90 fall into 50-100 (count 3).

2. Step 2: Check output format

   Output counts per bucket: {_id: 0, count: 2} and {_id: 50, count: 3}.

3. Final Answer:

   [{_id: 0, count: 2}, {_id: 50, count: 3}] -> Option C

4. Quick Check:

   Bucket counts match boundaries = A [OK]

Hint: Count docs per boundary range carefully [OK]

Common Mistakes:

• Mixing counts between buckets
• Misunderstanding boundaries as inclusive/exclusive
• Assuming default bucket is used when not needed

4. You wrote this aggregation but get an error:

{ $bucket: { groupBy: "$age", boundaries: [20, 30, 40], default: "Other" } }

The error says: "Boundaries must be sorted in ascending order and unique." What is the likely cause?

medium

A. Boundaries array is missing the lowest value 0.

B. Boundaries array is not sorted or has duplicates.

C. The default value must be a number, not a string.

D. The groupBy field must be an integer, not a string.

Solution

1. Step 1: Understand error message

   The error says boundaries must be sorted ascending and unique, so check boundaries array.

2. Step 2: Check boundaries array

   If boundaries are not sorted or have duplicates, error occurs. The example boundaries [20, 30, 40] are sorted and unique, so likely in actual code they are not.

3. Final Answer:

   Boundaries array is not sorted or has duplicates. -> Option B

4. Quick Check:

   Boundaries must be sorted unique = B [OK]

Hint: Check boundaries array order and duplicates first [OK]

Common Mistakes:

• Ignoring error message details
• Thinking default value type causes this error
• Assuming groupBy field type causes this error

5. You want to create 4 buckets automatically for a collection with a wide range of numeric values in field price. Which aggregation stage correctly achieves this using $bucketAuto?

hard

A. { $bucketAuto: { groupBy: "$price", buckets: 4, output: { count: { $sum: 1 }, avgPrice: { $avg: "$price" } } } }

B. { $bucket: { groupBy: "$price", boundaries: [0, 25, 50, 75, 100] } }

C. { $bucketAuto: { groupBy: "$price", boundaries: [0, 25, 50, 75, 100] } }

D. { $bucketAuto: { groupBy: "$price", buckets: "4" } }

Solution

1. Step 1: Identify correct $bucketAuto usage

   $bucketAuto requires groupBy and buckets (number). { $bucketAuto: { groupBy: "$price", buckets: 4, output: { count: { $sum: 1 }, avgPrice: { $avg: "$price" } } } } uses these correctly and includes output aggregation.

2. Step 2: Eliminate incorrect options

   { $bucket: { groupBy: "$price", boundaries: [0, 25, 50, 75, 100] } } uses $bucket with manual boundaries, not automatic. { $bucketAuto: { groupBy: "$price", boundaries: [0, 25, 50, 75, 100] } } incorrectly uses boundaries with $bucketAuto. { $bucketAuto: { groupBy: "$price", buckets: "4" } } uses string for buckets count, which must be a number.

3. Final Answer:

   { $bucketAuto: { groupBy: "$price", buckets: 4, output: { count: { $sum: 1 }, avgPrice: { $avg: "$price" } } } } -> Option A

4. Quick Check:

   Correct $bucketAuto syntax with numeric buckets = A [OK]

Hint: Use numeric buckets count and no boundaries with $bucketAuto [OK]

Common Mistakes:

• Using boundaries with $bucketAuto
• Passing buckets as string instead of number
• Confusing $bucket and $bucketAuto syntax