I'm trying to get the "top" 2 items for any number of foreign keys, sorted by some key. What I have is the following, which appears to work:

    {$match: {fk: {$in: [1, 2]}}}
    {$sort: {name: -1}}, 
    {$group: {_id: "$fk", items: {$push: "$$ROOT"} }}, 
    {$project: {items: {$slice: ["$items", 2]} }}

My question is: does MongoDB guarantee that the sorting I apply in the second step in my aggregation via $sort will be maintained when I get down to the $slice inside my $project in the last step of my aggregation?

The data I'm seeing indicates that MongoDB is currently behaving this way, but I'm wondering if this is spec'd or if MongoDB is free to return the items array in a different order if the optimizer ever decides it would be advantageous to do so.


Your conclusion is correct: internal optimisations or implementation details may alter the order of results depending on the stage.

The $group stage is intentionally not order preserving, so you cannot rely on observational behaviour.

As noted in discussion on SERVER-24799: $group aggregation command should maintain document order in the MongoDB issue tracker:

The reason the order is not preserved is that we keep track of all groups with a map from the _id to the accumulated value, so that we can quickly look up which group an incoming document belongs to.

As per Aggregation Pipeline Optimizations, some pipeline stages may also be coalesced or reordered to equivalent pipelines with improved performance. You can use the explain:true option to return information about how a pipeline will be executed.


While the accepted answer is correct in that $group stage will not preserver order, I think it left some important information out and can be misleading.

If you look at the comments on the Jira Ticket linked it clears it up there to. Basically it says that $group maintains the order within the 'groups' but order will not be guaranteed for stages after the group stage.

So $items will be sorted by name: -1 in the example and calling $slice 2 on it in the $project stage will result in the first 2 items sorted by name.

So I guess for example if you have the following data

  { fk: 1, name: 'James' },
  { fk: 2, name: 'Zelda' },
  { fk: 2, name: 'Victor' },
  { fk: 1, name: 'Becky' },
  { fk: 1, name: 'Carlos' },
  { fk: 2, name: 'Katie' },

Running the example query

  { $match: { fk: { $in: [1, 2] } } },
  { $sort: { name: -1 } },
  { $group: { _id: "$fk", items: { $push: "$$ROOT" } } },
  { $project: { items: {$slice: ["$items", 2] } } }

You would get

{ _id: 2, items: [ { fk: 2, name: "Zelda" }, { fk: 2, name: "Victor" }] }
{ _id: 1, items: [ { fk: 1, name: "James" }, { fk: 1, name: "Carlos" }] }

which returns the first 2 names in descending order

But if you changed the sort by to be on fk

  { $match: { fk: { $in: [1, 2] } } },
  { $sort: { fk: -1 } },
  { $group: { _id: "$fk", items: { $push: "$$ROOT" } } },
  { $project: { items: {$slice: ["$items", 2] } } }

you could see something like

{ _id: 1, items: [ { fk: 1, name: "James" }, { fk: 1, name: "Becky" } ] }
{ _id: 2, items: [ { fk: 2, name: "Zelda" }, { fk: 2, name: "Victor" } ] }

where you can see that _id (which is fk) is not sorted in descending order. If you wanted it to be sorted by _id you could just add that sorting after the $group stage

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.