summaryrefslogtreecommitdiff
path: root/src/mongo/db/pipeline/parsed_inclusion_projection_test.cpp
Commit message (Collapse)AuthorAgeFilesLines
* SERVER-42288 Consolidate Document and WorkingSetMember metadata implementations.David Storch2019-07-261-2/+2
|
* 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-35493 Refactor Inclusion- and ExclusionNode into ProjectionNode base ↵Bernard Gorman2018-10-261-114/+75
| | | | class
* SERVER-37651 Update header files with new licenseRamon Fernandez2018-10-221-8/+10
|
* SERVER-35325 Implement key generation for "allPaths" indexesBernard Gorman2018-07-131-90/+314
|
* SERVER-35329 Package agg projection code for use outside of agg executionBernard Gorman2018-06-221-16/+16
|
* SERVER-30580 Eliminate UserException and MsgAssertionException typesMathias Stearn2017-08-161-2/+2
| | | | All users were converted to just use AssertionException.
* SERVER-29935 Clarify SingleDocumentTransformation's explain.Charlie Swanson2017-07-031-16/+16
| | | | | It's slightly different than that on DocumentSource, which should be more obvious.
* SERVER-20092: Add ability for DocumentSourceCursor to coalesce with a stage ↵Nick Zolnierz2017-05-231-0/+98
| | | | if it is doing an equivalent projection
* SERVER-28651 Move agg var ownership to ExpressionContextJames Wahlin2017-04-291-89/+79
|
* SERVER-19758 add support for "executionStats" and "allPlansExecution" to agg ↵David Storch2017-03-131-8/+28
| | | | | | | | | | | | | | | | | 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-25535 Remove injectExpressionContext().Charlie Swanson2016-12-161-43/+90
| | | | | | | | | | | | | | | These methods were formally used to propagate a new ExpressionContext to stages, accumulators, or expressions which potentially needed to comparisons. Originally, this was necessary since Pipeline parsing happened outside of the collection lock and thus could not determine if there was a default collation on the collection. This meant that the collation could change after parsing and any operators that might compare strings would need to know about it. We have since moved parsing within the lock, so the collation can be known at parse time and the ExpressionContext should not change. This patch requires an ExpressionContext at construction time, and disallows changing the collation on an ExpressionContext.
* SERVER-25992 Remove Value(const char* value) constructorTess Avitabile2016-12-161-55/+58
|
* SERVER-19153 push $match as far forward as possibleDavid Storch2016-10-061-0/+42
|
* SERVER-24508 DocumentComparator and ValueComparatorDavid Storch2016-07-141-48/+49
| | | | | | | | | | | - Changes the Document/Value library to require comparisons to be made in the context of a comparator object. This is prep work for full collation support in the aggregation system. - Adds injectExpressionContext() to propagate the ExpressionContext containing the comparator object to all DocumentSource, Accumulator, and Expression instances involved in the Pipeline.
* SERVER-18966 Add the ability to exclude fields in $project stageCharlie Swanson2016-06-241-0/+545
View Lorry Controller Status