Aggregate¶
Runs a MongoDB aggregation pipeline on a collection : the body is the array of stages, the answer their result.
| Method | POST |
| URL | /api/schema/admin/mongodb/inventory/customers/aggregate |
| Body | the pipeline : an array of stages |
| Query params | none |
| Answer | data : the documents produced by the pipeline |
| Databases | MongoDB only |
| Cached | yes, with enableCaching on the table |
| From code | g.sys.db.aggregate |
| API id | SCHEMA_POST_AGGREGATE (groups, settings, hooks, WebSocket subscriptions) |
| Without a schema | /api/gen/admin/mongodb/inventory/customers/aggregate : below |
Generated (/api/gen) or schema (/api/schema) ?
Both families offer the same operations on the same URL pattern. The schema APIs read the schema of the table : values are converted to their types, validated, encrypted, defaulted and numbered before they reach the database. The generated APIs are schemaless : they pass your data as it is, so a number sent as "22" stays a string. Use the schema APIs for the tables your application writes to, and the generated APIs for quick reads and for tables without a schema.
The URL¶
/api/schema/admin/mongodb/inventory/customers/aggregate : replace admin with the user path of your account, mongodb with your instance, inventory with the database and customers with the table. The examples use this table :
| customer_id | first_name | last_name | last_update | pincode | isActive |
|---|---|---|---|---|---|
| 1 | Bob | lin | 2022-11-14 04: 34: 58 | 382345 | 1 |
| 2 | Alice | Page | 2022-10-15 02: 10: 40 | 382346 | 1 |
| 3 | Mallory | Brown | 2022-09-13 03: 44: 05 | 382347 | 1 |
| 4 | Eve | Mathly | 2022-11-12 01: 59: 33 | 382348 | 1 |
| 5 | Eve | Page | 2022-11-12 01: 59: 33 | 382349 | 1 |
The call¶
[
{ "$match": { "status": "PAID" } },
{ "$group": { "_id": "$customer_id", "orders": { "$sum": 1 }, "total": { "$sum": "$total" } } },
{ "$sort": { "total": -1 } },
{ "$limit": 10 }
]
- A body which is not an array is refused with
Please provide array for aggregate body.
Stages¶
Every stage of the MongoDB version you run is accepted. The ones used most :
| Stage | Example |
|---|---|
$match |
{ "$match": { "pincode": { "$gt": 380000 } } } |
$group |
{ "$group": { "_id": "$pincode", "count": { "$sum": 1 } } } |
$project |
{ "$project": { "name": { "$toLower": "$first_name" } } } |
$addFields |
{ "$addFields": { "full_name": { "$concat": [ "$first_name", " ", "$last_name" ] } } } |
$sort, $skip, $limit |
{ "$sort": { "total": -1 } } |
$count |
{ "$count": "customers" } |
$bucket |
{ "$bucket": { "groupBy": "$price", "boundaries": [ 0, 100, 500 ], "default": "Other", "output": { "count": { "$sum": 1 } } } } |
$facet |
several pipelines in one : { "$facet": { "byPrice": [ … ], "byCategory": [ … ] } } |
$lookup |
a join inside MongoDB : { "$lookup": { "from": "orders", "localField": "customer_id", "foreignField": "customer_id", "as": "orders" } } |
$unwind |
{ "$unwind": "$orders" } |
$collStats |
{ "$collStats": { "storageStats": {}, "count": {} } } |
With a schema¶
- The
findof a first$matchstage is converted with the schema (types, ObjectIds, dotted keys of relations), so{ "$match": { "customer_id.loyalty_tier": "GOLD" } }filters through the tablecustomer_idrefers to, as a find and join.
Good to know¶
- Only MongoDB : SQL databases answer
This API is only supported for mongodb.For SQL, run a query with executeQuery from a custom API. - Field permissions of the groups apply to what a stage returns. A caller who can not read a field does not get it, projected or not.
- With caching on, a pipeline answers from Redis until the collection changes.
From your code¶
g.sys.db.aggregate makes the same call from custom APIs, hooks, events, schedulers and test cases, with the same headers and params. To get the whole response envelope instead of data, pass true as the second argument in TypeScript, or call it through g.sys.db.full in the other languages.
Without a schema : /api/gen¶
Every table also answers this operation under /api/gen, with or without a schema :
| URL | /api/gen/admin/mongodb/inventory/customers/aggregate |
| API id | GEN_POST_AGGREGATE (groups, settings, hooks, WebSocket subscriptions) |
| From code | g.sys.db.gen.aggregateGen |
The data passes as it is : nothing is converted, validated, defaulted, encrypted or numbered, and a filter matches the type you send ("22" does not match the number 22). On MongoDB, strings which look like ObjectIds are converted. The query params, headers and errors are the ones of this page.
Headers¶
Every call takes the request headers : the tokens, x-am-response-case, x-am-content-type-response (JSON, XML, YAML…), x-am-response-object-type: make_flat, x-am-cache-control, x-am-get-encrypted-data, x-am-internationalization, x-am-tenant-username, x-am-meta.
Errors¶
| Code | When |
|---|---|
401 |
The token in x-am-authorization is missing or invalid. |
403 |
No group of the API user grants this API of this table, or a field of the request. |
404 |
The instance, database or table of the URL does not exist, or the table has no schema (use /api/gen). |
400 |
The query or the body is wrong : the error messages say which key and why. |
Related¶
- All APIs at a glance · Query params · Response format · Pre hooks and post hooks · Automatic caching
- Table schema : what the conversions and validations do to every write.