You are browsing a version that has not yet been released.
Maintained
2.10 (upcoming) 2.9.1 (current)
Unmaintained
2.8 2.7 2.6 2.5 2.4 2.3 2.2 2.1 2.0 1.3 1.2 1.1 1.0

Aggregation builder

The aggregation framework provides an easy way to process records and return computed results. The aggregation builder helps to build complex aggregation pipelines.

Creating an Aggregation Builder

You can create a new Aggregation\Builder object with the DocumentManager::createAggregationBuilder() method:

1<?php

$builder = $dm->createAggregationBuilder(\Documents\User::class);


2


3

The first argument indicates the document for which you want to create the builder.

Adding pipeline stages

To add a pipeline stage to the builder, call the corresponding method on the builder object:

1<?php

$builder = $dm->createAggregationBuilder(\Documents\Orders::class);
$builder
    ->match()
        ->field('purchaseDate')
        ->gte($from)
        ->lt($to)
        ->field('user')
        ->references($user)
    ->group()
        ->field('id')
        ->expression('$user')
        ->field('numPurchases')
        ->sum(1)
        ->field('amount')
        ->sum('$amount');


2


3


4


5


6


7


8


9


10


11


12


13


14


15


16


17

Just like the query builder, the aggregation builder takes care of converting DateTime objects into MongoDB\Driver\BSON\UTCDateTime objects.

Nesting expressions

You can create more complex aggregation stages by using the expr() method in the aggregation builder.

1<?php

$builder = $dm->createAggregationBuilder(\Documents\Orders::class);
$builder
    ->match()
        ->field('purchaseDate')
        ->gte($from)
        ->lt($to)
        ->field('user')
        ->references($user)
    ->group()
        ->field('id')
        ->expression(
            $builder->expr()
                ->field('month')
                ->month('$purchaseDate')
                ->field('year')
                ->year('$purchaseDate')
        )
        ->field('numPurchases')
        ->sum(1)
        ->field('amount')
        ->sum('$amount');


2


3


4


5


6


7


8


9


10


11


12


13


14


15


16


17


18


19


20


21


22


23

This aggregation would group all purchases by their month and year by projecting those values into an embedded object for the id field. For example:

1{
    _id: {
        month: 1,
        year: 2016
    },
    numPurchases: 1,
    amount: 27.89
}


2


3


4


5


6


7


8

Executing an aggregation pipeline

When you are done building your pipeline, you can build an Aggregation object using the getAggregation() method. The returning instance can yield a single result or return an iterator containing all results.

1<?php

$builder = $dm->createAggregationBuilder(\Documents\User::class);
$result = $builder->getAggregation();


2


3


4

If you instead want to look at the built aggregation pipeline, call the Builder::getPipeline() method.

Hydration

By default, aggregation results are returned as PHP arrays. This is because the result of an aggregation pipeline may look completely different from the source document. In order to get hydrated aggregation results, you first have to map a QueryResultDocument. These are written like regular mapped documents, but they can't be persisted to the database.

1<?php

namespace Documents;

#[QueryResultDocument]
class UserPurchases
{
    #[ReferenceOne(targetDocument: User::class, name: '_id')]
    private User $user;

    #[Field(type: 'int')]
    private int $numPurchases;

    #[Field(type: 'float')]
    private float $amount;
}


2


3


4


5


6


7


8


9


10


11


12


13


14


15


16

Once you have mapped the document, use the hydrate() method to tell the aggregation builder about this document:

1<?php

$builder = $dm->createAggregationBuilder(\Documents\Orders::class);
$builder
    ->hydrate(\Documents\UserPurchases::class)
    ->match()
        ->field('purchaseDate')
        ->gte($from)
        ->lt($to)
        ->field('user')
        ->references($user)
    ->group()
        ->field('id')
        ->expression('$user')
        ->field('numPurchases')
        ->sum(1)
        ->field('amount')
        ->sum('$amount');


2


3


4


5


6


7


8


9


10


11


12


13


14


15


16


17


18

When you run the queries, all results will be returned as instances of the specified document.

Query result documents can use all features regular documents can use: you can map embedded documents, define references, and even use discriminators to get different result documents according to the aggregation result.

Disabling Result Caching

Due to MongoDB cursors not being rewindable, ODM uses a caching iterator when returning results from aggregation pipelines. This cache allows you to iterate a result cursor multiple times without re-executing the original aggregation pipeline. However, in long-running processes or when handling a large number of results, this can lead to high memory usage. To disable this result cache, you can tell the query builder to not return a caching iterator:

1<?php

$builder = $dm->createAggregationBuilder(\Documents\Orders::class);
$builder->rewindable(false);


2


3


4

When setting this option to false, attempting a second iteration will result in an exception. Note that calling getAggregation() will always yield a fresh aggregation instance that can be re-executed.