Change stream pipelines for filtering in MongoDB - Step-by-Step Execution

Concept Flow - Change stream pipelines for filtering

Start watching collection

↓

Receive change event

↓

Apply pipeline filter

↓

Emit event

↓

Wait for next event

This flow shows how MongoDB change streams receive events, apply filters using a pipeline, and emit only matching events.

Execution Sample

MongoDB

db.collection.watch([
  { $match: { 'fullDocument.status': 'active' } }
])

This pipeline watches a collection and only emits change events where the document's status is 'active'.

Execution Table

Step	Change Event Received	Pipeline Filter Condition	Filter Result	Action
1	{_id:1, fullDocument:{status:'active'}}	status == 'active'	True	Emit event
2	{_id:2, fullDocument:{status:'inactive'}}	status == 'active'	False	Ignore event
3	{_id:3, fullDocument:{status:'active'}}	status == 'active'	True	Emit event
4	{_id:4, fullDocument:{status:'pending'}}	status == 'active'	False	Ignore event
5	No more events	-	-	Stop watching

💡 No more change events to process, watching ends.

Variable Tracker

Variable	Start	After 1	After 2	After 3	After 4	Final
Current Event	null	{_id:1, status:'active'}	{_id:2, status:'inactive'}	{_id:3, status:'active'}	{_id:4, status:'pending'}	null
Filter Result	null	True	False	True	False	null
Emitted Events Count	0	1	1	2	2	2

Key Moments - 2 Insights

Why does the event with status 'inactive' get ignored?

Because the pipeline filter only allows events where status is 'active' (see execution_table row 2), so 'inactive' does not pass the filter.

What happens if no events match the filter?

No events are emitted; the change stream waits for new events but does not output anything until a matching event arrives (see execution_table rows 2 and 4).

Visual Quiz - 3 Questions

Look at the execution table, how many events were emitted after step 3?

A 3

B 2

C 1

D 0

💡 Hint

Check the 'Emitted Events Count' column in variable_tracker after step 3.

At which step does the filter condition evaluate to False for the first time?

A Step 1

B Step 3

C Step 2

D Step 4

💡 Hint

Look at the 'Filter Result' column in execution_table for each step.

If the pipeline filter changed to status == 'pending', how many events would be emitted by step 4?

A 1

B 2

C 3

D 0

💡 Hint

Check which events have status 'pending' in the 'Change Event Received' column.

Concept Snapshot

Change stream pipelines filter events in MongoDB.
Use $match stage to specify conditions.
Only events matching the filter are emitted.
Non-matching events are ignored silently.
Useful to watch specific changes efficiently.

Full Transcript

This visual execution shows how MongoDB change streams use pipelines to filter events. The stream receives change events from a collection. Each event is checked against the pipeline filter condition, for example, matching documents with status 'active'. If the event matches, it is emitted to the client. If not, it is ignored. The process repeats for each event until no more events arrive. Variables like current event, filter result, and emitted events count change step by step. This helps beginners see exactly how filtering works in change streams.