Time-series collections in MongoDB - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a time-series collection in MongoDB?

A time-series collection is a special type of collection optimized to store and query data that changes over time, like sensor readings or logs, making it faster and more efficient for time-based data.

beginner

Which two fields are used when creating a time-series collection in MongoDB?

The two fields are the timeField, which stores the timestamp of the data, and the metaField, which stores metadata about the data points.

intermediate

How does MongoDB optimize storage for time-series collections?

MongoDB organizes data in time-series collections by grouping measurements into compressed internal buckets based on time intervals, reducing storage space and improving query speed.

intermediate

Can you insert regular documents into a time-series collection in MongoDB?

No, time-series collections expect documents to follow a specific schema with a timeField and optional metaField. Regular documents without these fields will cause errors or unexpected behavior.

beginner

What is the benefit of using the metaField in a time-series collection?

The metaField stores metadata that groups related measurements, like device ID or location, allowing efficient filtering and querying without duplicating data in every document.

What is the purpose of the timeField in a MongoDB time-series collection?

A To index the collection

B To store the timestamp of each data point

C To store metadata about the data

D To store user information

The timeField stores the timestamp for each measurement, which is essential for time-based queries.

Which command is used to create a time-series collection in MongoDB?

A db.createTimeSeries('name')

B db.createTimeSeriesCollection('name')

C db.createCollection('name')

D db.createCollection('name', { timeseries: { timeField: 'time' } })

You create a time-series collection by using db.createCollection with the timeseries option specifying the timeField.

What happens if you insert a document without the timeField into a time-series collection?

A The insert fails with an error

B The document is inserted normally

C The document is stored but ignored in queries

D The timeField is automatically added

Documents must have the timeField; otherwise, MongoDB rejects the insert.

Why are time-series collections more efficient for time-based data?

A They compress data and group it by time intervals

B They use more indexes

C They store data in multiple databases

D They require less disk space by deleting old data automatically

Time-series collections compress data into buckets based on time, improving storage and query efficiency.

What type of data is best suited for MongoDB time-series collections?

A Static product catalogs

B User profiles

C Sensor readings and logs

D Image files

Time-series collections are designed for data that changes over time, like sensor readings and logs.

Explain how MongoDB time-series collections store and organize data differently from regular collections.

Think about how time and metadata help group and compress data.

Describe the steps and key options needed to create a time-series collection in MongoDB.

Focus on the command and required fields.

Practice

1. What is the main purpose of a time-series collection in MongoDB?

easy

A. To manage user authentication and roles

B. To store large binary files like images and videos

C. To efficiently store and query data that changes over time

D. To create backups of the database automatically

Solution

1. Step 1: Understand time-series data

   Time-series data is data recorded over time, like temperature or stock prices.

2. Step 2: Identify MongoDB time-series collection use

   MongoDB time-series collections optimize storage and queries for such time-based data.

3. Final Answer:

   To efficiently store and query data that changes over time -> Option C

4. Quick Check:

   Time-series collections = efficient time-based data storage [OK]

Hint: Time-series collections are for data changing over time [OK]

Common Mistakes:

• Confusing time-series collections with file storage
• Thinking time-series collections manage users
• Assuming they handle backups automatically

2. Which of the following is required when creating a time-series collection in MongoDB?

easy

A. A field that stores binary data

B. A unique index on the _id field

C. A field that stores user roles

D. A field that stores the timestamp of each record

Solution

1. Step 1: Recall time-series collection requirements

   MongoDB requires a time field to track when each data point was recorded.

2. Step 2: Check other options

   Unique _id index exists by default but is not specific to time-series; user roles and binary data fields are unrelated.

3. Final Answer:

   A field that stores the timestamp of each record -> Option D

4. Quick Check:

   Time field required = A field that stores the timestamp of each record [OK]

Hint: Time field is mandatory for time-series collections [OK]

Common Mistakes:

• Choosing unrelated fields like user roles
• Confusing default indexes with required time field
• Thinking binary data field is required

3. Given the following command, what will be the result?

db.createCollection("sensorData", {
  timeseries: {
    timeField: "timestamp",
    metaField: "deviceId"
  }
})

medium

A. Creates a time-series collection with timestamp and deviceId fields

B. Throws a syntax error due to missing options

C. Creates a regular collection named sensorData

D. Creates a capped collection instead of time-series

Solution

1. Step 1: Analyze the createCollection command

   The command uses the timeseries option with timeField and metaField specified.

2. Step 2: Understand MongoDB behavior

   This creates a time-series collection named sensorData with timestamp as time and deviceId as metadata.

3. Final Answer:

   Creates a time-series collection with timestamp and deviceId fields -> Option A

4. Quick Check:

   timeseries option creates time-series collection [OK]

Hint: timeseries option creates time-series collection [OK]

Common Mistakes:

• Thinking it creates a regular or capped collection
• Assuming syntax error due to missing options
• Confusing metaField with required timeField

4. You tried to create a time-series collection but got an error. Which of the following is the most likely cause?

db.createCollection("temps", {
  timeseries: {
    metaField: "location"
  }
})

medium

A. Missing required timeField in timeseries options

B. metaField cannot be used in time-series collections

C. Collection name is invalid

D. timeseries option is misspelled

Solution

1. Step 1: Check timeseries options in the command

   The command specifies metaField but omits the required timeField.

2. Step 2: Recall MongoDB requirements

   timeField is mandatory for time-series collections; missing it causes an error.

3. Final Answer:

   Missing required timeField in timeseries options -> Option A

4. Quick Check:

   timeField missing = error [OK]

Hint: Always include timeField when creating time-series collections [OK]

Common Mistakes:

• Thinking metaField is not allowed
• Assuming collection name is invalid
• Believing timeseries option is misspelled

5. You have a time-series collection with fields timestamp (timeField) and sensorId (metaField). You want to query the average temperature for sensorId 'S1' over the last 24 hours. Which aggregation pipeline is correct?

db.sensorData.aggregate([
  { $match: { sensorId: 'S1', timestamp: { $gte: new Date(Date.now() - 86400000) } } },
  { $group: { _id: null, avgTemp: { $avg: "$temperature" } } }
])

hard

A. Groups by sensorId instead of null

B. Correctly filters by sensorId and timestamp, then averages temperature

C. Uses $sort instead of $match for filtering

D. Filters only by timestamp, ignoring sensorId

Solution

1. Step 1: Analyze the $match stage

   The pipeline filters documents where sensorId is 'S1' and timestamp is within last 24 hours.

2. Step 2: Analyze the $group stage

   It groups all matched documents (_id: null) and calculates average temperature.

3. Final Answer:

   Correctly filters by sensorId and timestamp, then averages temperature -> Option B

4. Quick Check:

   Filter by sensorId and time, then average = Correctly filters by sensorId and timestamp, then averages temperature [OK]

Hint: Match filters, group aggregates for averages [OK]

Common Mistakes:

• Forgetting to filter by sensorId
• Using $sort instead of $match for filtering
• Grouping by sensorId when only one sensor is queried