| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
confusion with $merge
|
|
|
|
|
|
|
| |
This stage is distinguished from the Mock stage in that it doesn't
bother tracking state about which methods have been called. The queue
version is simpler and is used in production code (namely the update
system), whereas the mock is still preferred in testing environments.
|
|
|
|
| |
This bans $merge and $sB from $lookup subpipelines
|
|
|
|
| |
This commit also renames DocumentSourceMock::create to DocumentSourceMock::createForTest.
|
|
|
|
| |
This reverts commit 1b00abfda7592d701f632b9550f973c56cea818f.
|
|
|
|
| |
encryption in agg
|
|
|
|
|
|
| |
The streaming $group optimization was never fully implemented,
so the code was disabled. This patch removes the dead code, including
DocumentSource::getOutputSorts().
|
|
|
|
|
|
| |
Remove leading comments that are just stating the filename.
Move any file-level comments below the copyright banner.
Remove leading blank lines.
|
|
|
|
|
| |
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.
|
|
|
|
| |
This reverts commit 0cb2195939494660334db8e9d0a52509caeb621c.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
requirements, given pipeline split state
|
|
|
|
| |
allowDiskUse is false
|
|
|
|
| |
union should merge on mongos
|
|
|
|
| |
This reverts commit babab967892f81f3107903cb41672503de791998.
|
|
|
|
| |
This reverts commit 2431e1356823d898ef8af16997d6f63b65b385a5.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Ensures that a collection lock is held in at least MODE_IS while
deregistering a PlanExecutor from the cursor manager. Introduces new
PlanExecutor::dispose() and ClientCursor::dispose() methods that must be
called before destruction of those classes, and ensures they are called
before destruction. These calls will thread an OperationContext all the
way through to DocumentSource::dispose() for each stage in a Pipeline,
which will give DocumentSourceCursor a chance to acquire locks and
deregister its PlanExecutor if necessary.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|