From the `activityLogs`, count the number of actions per user, get the average actions, and return users with more than 2 actions.
Problem Statement
Examples
Input: activityLogs collection: +-----+--------+----------+ | _id | userId | action | +-----+--------+----------+ | 1 | u1 | login | | 2 | u2 | login | | 3 | u1 | purchase | | 4 | u1 | logout | | 5 | u3 | login | | 6 | u2 | purchase | +-----+--------+----------+
Output: +-----+-------------+ | _id | actionCount | +-----+-------------+ | u1 | 3 | +-----+-------------+
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 "User Activity Report", we query the MongoDB document store. The goal is to from the `activitylogs`, count the number of actions per user, get the average actions, and return users with more than 2 actions. 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.activityLogs.aggregate([
{ $group: { _id: "$userId", actionCount: { $sum: 1 } } },
{ $match: { actionCount: { $gt: 2 } } }
]);
}
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.