-
Type: Improvement
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Aggregation Framework, Querying
-
None
-
Fully Compatible
-
Query 2017-04-17, Query 2017-05-08, Query 2017-05-29, Query 2019-03-11, Query 2019-03-25, Query 2019-04-08
-
(copied to CRM)
-
0
An aggregation pipeline can be used to represent a query, like the following:
db.example.aggregate([{$project: {excluded: 0}}, {$match: {predicate: true}}]);
In these cases, it would be more efficient to skip the aggregation layer, and execute the entire computation using a query.
It is expected that pipelines like the above pipeline will be much more common once non-materialized views are introduced in SERVER-142.
- causes
-
PHPLIB-431 Relax aggregate explain test for 4.2 servers
- Closed
-
RUBY-1788 Aggregate explain broken on 4.2 server
- Closed
- is depended on by
-
SERVER-45069 Add flag in the log when aggregation is using query code path
- Closed
- is duplicated by
-
SERVER-36983 Views are unnecessary slow, even for very simple views
- Closed
- is related to
-
SERVER-40253 Pipelines with text search queries should be eligible for being optimized away
- Closed
-
SERVER-40254 Collapse project stage in a pipeline so the projection occurs in DocumentSourceCursor
- Closed
-
SERVER-40323 Plan analyzer helper functions cannot correctly handle explain output for sharded collections
- Closed
-
SERVER-36723 $limit should push down into the PlanStage layer, rather than coalescing with DocumentSourceCursor
- Closed
- related to
-
SERVER-7568 Aggregation framework favors non-blocking sorts
- Closed
- mentioned in
-
Page Loading...