[SERVER-60139] Support group pushdown in pipeline optimization tests Created: 22/Sep/21 Updated: 29/Oct/23 Resolved: 22/Sep/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | Backlog |
| Fix Version/s: | 5.1.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Eric Cox (Inactive) | Assignee: | Eric Cox (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Steps To Reproduce: | ./buildscripts/resmoke.py run --mongodSetParameter=' {internalQueryEnableSlotBasedExecutionEngine: true}' --mongodSetParameter=' {featureFlagSBEGroupPushdown: true}' --suites=aggregation jstests/aggregation/optimize_away_pipeline.js |
| Sprint: | QE 2021-10-04 |
| Participants: |
| Description |
|
This test explicitly tests for a list of expected stages in the explain plan, for example:
Now when we push group down, there will be an extra group stage. All we need to do is update the `expectedStages` list to check for the GROUP stage when we know $group will be pushed down. |
| Comments |
| Comment by Vivian Ge (Inactive) [ 06/Oct/21 ] |
|
Updating the fixversion since branching activities occurred yesterday. This ticket will be in rc0 when it’s been triggered. For more active release information, please keep an eye on #server-release. Thank you! |
| Comment by Githook User [ 22/Sep/21 ] |
|
Author: {'name': 'Eric Cox', 'email': 'eric.cox@mongodb.com', 'username': 'ericox'}Message: |