summaryrefslogtreecommitdiff
path: root/src/mongo/db/pipeline/aggregation_request.h
Commit message (Collapse)AuthorAgeFilesLines
* SERVER-43860 Always upsert exact source document for pipeline-insert $merger4.2.2-rc0Bernard Gorman2019-12-031-0/+13
| | | | | (cherry picked from commit 23e55cb3d041236f399f7095df31cd3e3da491cc) (cherry picked from commit 70ef84cd14388602b3d763b12c6f8448ba62a9d8)
* SERVER-40397 Add pipeline updates to findAndModifyCharlie Swanson2019-04-301-1/+17
| | | | | | Adds the ability to specify an array representing an aggregation pipeline to the 'udpate' argument of findAndModify. Certain options like 'sort' and 'fields' are not yet supported.
* SERVER-40209 Implement $$NOW and $$CLUSTER_TIMEMartin Neupauer2019-03-261-0/+14
|
* SERVER-39560 - remove leading blank line on all C++ filesBilly Donahue2019-02-131-1/+0
| | | | | | Remove leading comments that are just stating the filename. Move any file-level comments below the copyright banner. Remove leading blank lines.
* SERVER-38038 mongo shell should support all ErrorExtraInfo codesMathias Stearn2019-01-231-1/+2
|
* SERVER-38410 Allow ARM to consume postBatchResumeTokenBernard Gorman2019-01-091-0/+22
|
* SERVER-37191 writeConcern for $outNick Zolnierz2018-10-311-0/+12
|
* SERVER-37651 Update header files with new licenseRamon Fernandez2018-10-221-8/+10
|
* SERVER-35899 Have mongos produce an aggregation plan that correctly uses an ↵Martin Neupauer2018-09-191-1/+1
| | | | $exchange.
* SERVER-35905 Plug pieces together to perform a distributed when applicableMartin Neupauer2018-08-301-0/+15
|
* SERVER-30924 Remove handling of 'fromRouter' in aggregation subsystem.David Storch2017-12-131-18/+0
| | | | | This code was necessary only to handle 3.4/3.6 mixed version clusters.
* SERVER-31665 Use correct read concern/preference during update lookupCharlie Swanson2017-11-171-1/+1
|
* SERVER-30899 Aggregations sent from a 3.4 mongos should serialize 3.4 metadataTess Avitabile2017-09-061-6/+24
|
* SERVER-18940 Optimise sharded aggregations that are targeted to a single shardBernard Gorman2017-08-021-0/+17
|
* SERVER-19318 Add $currentOp aggregation stage for mongoDBernard Gorman2017-05-261-0/+16
|
* SERVER-29072 Add support for $lookup into a sub-pipelineJames Wahlin2017-05-191-0/+6
|
* SERVER-28983 Fix undefined behaviour for the 'aggregate' commandKaloian Manassiev2017-04-271-12/+12
|
* SERVER-28040 Fix maxTimeMS/readPref/readConcern for sharded view queryJames Wahlin2017-04-051-0/+34
|
* SERVER-28128 Add support for a "comment" parameter to the aggregate...Bernard Gorman2017-03-151-0/+12
| | | ... command
* SERVER-19758 add support for "executionStats" and "allPlansExecution" to agg ↵David Storch2017-03-131-9/+21
| | | | | | | | | | | | | | | | | explain Like other explainable commands, aggregate can now be explained using the explain command, e.g. db.runCommand({explain: {aggregate: ...}, verbosity: "executionStats"}). The existing explain:true flag corresponds to "queryPlanner" mode and is still supported. However, explain:true cannot be specified when explaining aggregate via the explain command. Additional execution information is provided only in the $cursor section of the aggregation explain output. Having aggregation stages themselves track and report execution info is further work.
* SERVER-27848 Add index hint to aggregation and non-materialized viewsJames Wahlin2017-02-031-0/+14
|
* SERVER-24623 Remove single document aggregation result optionTess Avitabile2017-01-131-14/+4
|
* SERVER-24762 Add cursor options to AggregationRequestJames Wahlin2016-07-071-0/+28
|
* SERVER-24638 Move command processing from Pipeline to AggregationRequestCharlie Swanson2016-06-241-0/+157