Group all subscriptions by `status` and count how many are in each group. Sort by count descending.
Problem Statement
Examples
Input: subscriptions collection: +-----+-----------+ | _id | status | +-----+-----------+ | 1 | active | | 2 | active | | 3 | cancelled | | 4 | active | | 5 | cancelled | | 6 | trial | +-----+-----------+
Output: +-----------+-------+ | _id | count | +-----------+-------+ | active | 3 | | cancelled | 2 | | trial | 1 | +-----------+-------+
Explanation: The query calculates the total count of documents that satisfy the given filter criteria.
Complexity
Time Complexity: -
Space Complexity: -
Hints
Editorial & Approach
Problem Overview & Intuition
To solve "Churn Analysis: Active vs Cancelled Count", we query the MongoDB document store. The goal is to group all subscriptions by `status` and count how many are in each group. sort by count descending. 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.subscriptions.aggregate([
{ $group: { _id: "$status", count: { $sum: 1 } } },
{ $sort: { count: -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.