summaryrefslogtreecommitdiff
path: root/src/mongo/db/pipeline/document_source_geo_near.h
Commit message (Collapse)AuthorAgeFilesLines
* 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-38311 Change out merging strategyCharlie Swanson2019-02-131-9/+2
| | | | | Allows an $out stage to run in parallel on all shards if the target collection is sharded and so is the input collection to the aggregate.
* SERVER-38716 fix $geoNear and $text within $lookup sub-pipelineBrigitte Lamarche2019-01-171-1/+2
|
* Revert " SERVER-38311 Adjust $out merging strategy"Charlie Swanson2019-01-161-2/+9
| | | | This reverts commit 0cb2195939494660334db8e9d0a52509caeb621c.
* SERVER-38311 Adjust $out merging strategyCharlie Swanson2019-01-161-9/+2
|
* SERVER-37651 Update header files with new licenseRamon Fernandez2018-10-221-21/+23
|
* SERVER-33323 Refactor agg cursor merging on mongosCharlie Swanson2018-08-151-1/+2
| | | | | | | | | | This commit makes it so that aggregations will always use a $mergeCursors as a wrapper around a AsyncResultsMerger, which is new behavior for mongos. As part of this refactor, we can delete the concept of a 'merging presorted' $sort stage (which is now handled by the AsyncResultsMerger) and delete the DocumentSourceRouterAdapter stage which talked to a RouterStageMerge, instead directly using a $mergeCursors stage.
* SERVER-35329 Package agg projection code for use outside of agg executionBernard Gorman2018-06-221-1/+1
|
* SERVER-35043, SERVER-22949: move geoNear implementation into aggregationKyle Suarez2018-06-181-51/+85
| | | | | | | | | | This commit removes the geoNear command and moves its implementation into the aggregation framework. Users should use the aggregate command with a $geoNear stage. The implementation rewrite additionally removes the limit in the $geoNear aggregation stage. To limit the number of results, use a $limit stage.
* SERVER-25596 Rename SplittableDocumentSource to NeedsMergerDocumentSourceKevinCybura2018-05-111-2/+2
| | | | | | Closes #1237 Signed-off-by: Charlie Swanson <charlie.swanson@mongodb.com>
* SERVER-33666 Make $geoNear stage and geoNear command support readConcern ↵James Wahlin2018-03-211-1/+1
| | | | level snapshot
* SERVER-33541 Add readConcern level 'snapshot' support for aggregation.David Storch2018-03-091-1/+2
|
* SERVER-32190 Make MongoProcessInterface always availableCharlie Swanson2017-12-191-2/+1
|
* SERVER-31651 Extend geoNear command and agg stage to accept optional 'key' ↵David Storch2017-12-011-0/+6
| | | | field.
* SERVER-29141 Enable change streams on sharded collectionsCharlie Swanson2017-10-091-1/+1
|
* SERVER-29141 Extend StageConstraints to allow kLocalOnly and kMongos host ↵Bernard Gorman2017-10-041-1/+1
| | | | requirements, given pipeline split state
* SERVER-29609 Rename MongodInterface to MongoProcessInterface.Charlie Swanson2017-10-031-1/+2
|
* SERVER-30871 Permit blocking aggregation stages to run on mongoS if ↵Bernard Gorman2017-09-271-3/+6
| | | | allowDiskUse is false
* SERVER-22760 Sharded aggregation pipelines which involve taking a simple ↵Bernard Gorman2017-08-081-1/+1
| | | | union should merge on mongos
* SERVER-29506 Require $changeNotification to be the first stage.Eddie Louie2017-08-011-2/+8
| | | | This reverts commit babab967892f81f3107903cb41672503de791998.
* Revert "SERVER-29506 Require $changeNotification to be the first stage."Eddie Louie2017-08-011-8/+2
| | | | This reverts commit 2431e1356823d898ef8af16997d6f63b65b385a5.
* SERVER-29506 Require $changeNotification to be the first stage.Charlie Swanson2017-08-011-2/+8
|
* SERVER-19318 Add $currentOp aggregation stage for mongoDBernard Gorman2017-05-261-2/+2
|
* SERVER-19758 add support for "executionStats" and "allPlansExecution" to agg ↵David Storch2017-03-131-1/+1
| | | | | | | | | | | | | | | | | 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-22632 Split up document_source.h into one header per stage.Charlie Swanson2016-10-241-0/+104