[SERVER-447] new aggregation framework Created: 29/Nov/09  Updated: 12/Jul/16  Resolved: 14/Mar/12

Status: Closed
Project: Core Server
Component/s: Aggregation Framework
Affects Version/s: None
Fix Version/s: 2.1.1

Type: New Feature Priority: Major - P3
Reporter: Eliot Horowitz (Inactive) Assignee: Chris Westin
Resolution: Done Votes: 79
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-4650 Malformed aggregation runCommand invo... Closed
depends on SERVER-3396 aggregation: $add with strings puts c... Closed
depends on SERVER-4359 Non-atomic reference counting in thre... Closed
depends on SERVER-4384 Grouping by incorrect projected field... Closed
depends on SERVER-4389 Wrong $eq format crashes Closed
depends on SERVER-4508 In new aggregation framework, when ex... Closed
depends on SERVER-4674 aggregation: treat undefined values ... Closed
depends on SERVER-4738 aggregation: field inclusion in $gro... Closed
depends on SERVER-4844 can't killop an aggregation operation Closed
depends on SERVER-4843 non user friendly assertion with skip:0 Closed
depends on SERVER-3253 aggregation: unsharded support $out Closed
depends on SERVER-3862 aggregation: add $first and $last gr... Closed
depends on SERVER-4435 aggregation: need a function to reco... Closed
depends on SERVER-10097 aggregation: support $out on a sharde... Closed
depends on DOCS-53 aggregation to SQL Mapping Chart Closed
depends on SERVER-3257 aggregation: create real error numbers Closed
depends on SERVER-3258 aggregation: assertion failure on em... Closed
depends on SERVER-3292 aggregation: add a limit option for ... Closed
depends on SERVER-3548 use field path prefix consistently on... Closed
depends on SERVER-3832 aggregation: early $sort should be o... Closed
depends on SERVER-3855 aggregation: finalize command name Closed
depends on SERVER-3856 aggregation: $unwind should be a sep... Closed
depends on SERVER-3857 aggregation: finalize name of $unwind Closed
depends on SERVER-3858 aggregation: finalize name of $project Closed
depends on SERVER-3860 aggregation: uassert on sorts where ... Closed
depends on SERVER-3861 aggregation: make $skip and $limit t... Closed
depends on SERVER-3865 aggregation: finalize field referenc... Closed
depends on SERVER-3881 aggregation: $group _id should suppor... Closed
depends on SERVER-3884 aggregation: add automated tests for... Closed
depends on SERVER-3252 aggregation: allow _id to be a non-s... Closed
depends on SERVER-3859 aggregation: if future updates use t... Closed
Related
related to SERVER-4961 $group is taking 2x as long as collec... Closed
related to SERVER-4438 aggregation: support nested pipeline... Backlog
related to SERVER-4929 aggregation: $group should have a $m... Backlog
related to SERVER-828 Support for selecting array elements ... Closed
related to SERVER-2293 Distinct can't process more than one key Closed
related to SERVER-4434 aggregation: add strptime functional... Closed
related to SERVER-4437 aggregation: support windowing opera... Closed
related to SERVER-4504 aggregation: need an explain facility Closed
related to SERVER-4899 aggregation: need an expression to g... Closed
related to SERVER-4507 aggregation: optimize $group to take... Backlog
related to SERVER-4445 aggregation: use a string table to r... Closed
related to SERVER-4506 aggregation: optimize by pushing mat... Closed
related to SERVER-4644 aggregation: optimize memory utilitz... Closed
related to SERVER-4656 aggregation: optimize sort/limit com... Closed
related to SERVER-4816 aggregation: optimize $sort on shard... Closed
related to SERVER-4930 aggregation: use dependency informat... Closed
is related to SERVER-326 Optimize MapReduce processing Closed
Participants:

 Description   

details forthcoming



 Comments   
Comment by Chris Westin [ 14/Mar/12 ]

Resolving: this roll-up ticket no longer has a purpose, now that we have an "Aggregation Framework" component for the server.

Comment by Chris Westin [ 14/Mar/12 ]

@Valentin Kuznetsov: For aggregation, that is covered by SERVER-4436. The plans is not to have a cursor in the first version (2.2), but to have this in a cursor form for a subsequent release.

Comment by Chris Westin [ 23/Feb/12 ]

This is a roll-up ticket. Bumped it to 2.1.2 since all the parts for 2.1.1 are done.

Comment by Valentin Kuznetsov [ 14/Nov/11 ]

Are you going to address issue SERVER-3141? Just want to have a link to this issue over here.

Comment by Remon van Vliet [ 14/Jun/11 ]

Is there a public build available where we can play around with this? If not, when do you anticipate this to happen (2.1.x?)

Comment by Eliot Horowitz (Inactive) [ 08/Jun/11 ]

No - it won't be ready in time for 2.0

Comment by Jeremy Smith [ 08/Jun/11 ]

Is there any chance of this getting put in the 2.0 release? It seemed like there was alot of interest in this at the MongoNYC talk.

Comment by Colin Mollenhour [ 04/Jun/11 ]

More info for anyone wanting to know what this will include: http://www.slideshare.net/cwestin63/mongodb-aggregation-mongosf-may-2011

Comment by Eliot Horowitz (Inactive) [ 14/May/11 ]

Map/reduce is not going to be removed and is still being improved.
This is different.

Comment by rajeev [ 13/May/11 ]

is there an update on this? will this feature replace map-reduce functionality or will it enhance current map reduce functionality?

Comment by Olivier Allouch [ 08/Apr/11 ]

Hi,
As a user, I'm particularly interested in a GROUP BY equivalent. I know that automatically looking for a SQL equivalent is stupid, but that's your fault: you spoiled me.

Comment by Remon van Vliet [ 05/Jan/11 ]

That would be a very good feature to have. I'd propose something simple like :

db.collection.max(criteria, field)
db.collection.min(criteria, field)
db.collection.avg(criteria, field)
db.collection.sum(criteria, field)
etc.

I'd suggest against db.collection.find(..).sum(field) due to the implication that sum is a cursor function rather than an aggregate function.

Comment by Eliot Horowitz (Inactive) [ 05/Jan/11 ]

There will be native functions for things like sum/avg/min/max.

Comment by Scott Hernandez (Inactive) [ 05/Jan/11 ]

Will this include native aggregation like sum/avg/min/max, or custom expressions/functions (not in js)?

Comment by Eliot Horowitz (Inactive) [ 02/Apr/10 ]

trying to keep 1.5/1.6 very focused on sharding + replica sets.
will try to get it out asap so we can go back to features like these

Generated at Thu Feb 08 02:54:08 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.