Use an aggregation pipeline with `$match` to find all orders with `status: "shipped"`.
Problem Statement
Examples
Input: orders collection: +-----+--------+---------+--------+ | _id | item | status | amount | +-----+--------+---------+--------+ | 1 | Laptop | shipped | 999 | | 2 | Phone | pending | 699 | | 3 | Tablet | shipped | 499 | +-----+--------+---------+--------+
Output: +-----+--------+---------+--------+ | _id | item | status | amount | +-----+--------+---------+--------+ | 1 | Laptop | shipped | 999 | | 3 | Tablet | shipped | 499 | +-----+--------+---------+--------+
Explanation: The query retrieves all documents from the collection that satisfy the specified filter criteria.
Complexity
Time Complexity: -
Space Complexity: -
Hints
Editorial & Approach
Problem Overview & Intuition
To solve "Aggregation: $match Stage", we query the MongoDB document store. The goal is to use an aggregation pipeline with `$match` to find all orders with `status: "shipped"`. Using an aggregation pipeline, the database engine filters and structures the BSON documents efficiently.
Step-by-Step Approach
- Identify Target Collection: Access the collection through the
dbinstance. - Construct Query / Pipeline: Build the aggregation stages ($match, $group, $sort, etc.).
- Resolve Cursor: Invoke
.toArray()to transform the query cursor into the required array of documents.
Optimal Implementation (MongoDB)
function solve(db) {
return db.orders.aggregate([{ $match: { status: "shipped" } }]);
}
Complexity Analysis
Key Considerations & Edge Cases
- Empty Collections: If no documents match, the query cleanly returns an empty array
[]. - Missing / NULL Fields: Missing fields in documents are handled safely without throwing runtime exceptions.
- Type Coercion: BSON types (ObjectId, Numbers, Strings) are compared strictly according to MongoDB specifications.