Group `vehicles` by `type`, compute average `mileage`, and filter only types with average mileage above `50000`.
Problem Statement
Examples
Input: vehicles collection: +-----+-------+---------+ | _id | type | mileage | +-----+-------+---------+ | 1 | truck | 80000 | | 2 | sedan | 30000 | | 3 | truck | 60000 | | 4 | sedan | 45000 | | 5 | van | 70000 | +-----+-------+---------+
Output: +-------+------------+ | _id | avgMileage | +-------+------------+ | truck | 70000 | | van | 70000 | +-------+------------+
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 "Fleet Management: Average Mileage Per Vehicle Type", we query the MongoDB document store. The goal is to group `vehicles` by `type`, compute average `mileage`, and filter only types with average mileage above `50000`. 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.vehicles.aggregate([
{ $group: { _id: "$type", avgMileage: { $avg: "$mileage" } } },
{ $match: { avgMileage: { $gt: 50000 } } },
{ $sort: { avgMileage: -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.