Project only the `name` and `price` fields (exclude `_id`) from the `menu` collection.
Problem Statement
Examples
Input: menu collection: +-----+--------+-------+----------+ | _id | name | price | calories | +-----+--------+-------+----------+ | 1 | Burger | 10 | 500 | | 2 | Salad | 8 | 200 | | 3 | Fries | 5 | 400 | +-----+--------+-------+----------+
Output: +--------+-------+ | name | price | +--------+-------+ | Burger | 10 | | Salad | 8 | | Fries | 5 | +--------+-------+
Explanation: The query projects only the requested document fields matching the criteria.
Complexity
Time Complexity: -
Space Complexity: -
Hints
Editorial & Approach
Problem Overview & Intuition
To solve "Aggregation: $project Stage", we query the MongoDB document store. The goal is to project only the `name` and `price` fields (exclude `_id`) from the `menu` collection. 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.menu.aggregate([{ $project: { _id: 0, name: 1, price: 1 } }]);
}
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.