[SERVER-58429] Implement planning from cache for queries with pushed down $group Created: 12/Jul/21 Updated: 29/Oct/23 Resolved: 19/Nov/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.2.0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Ian Boros | Assignee: | Irina Yatsenko (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Sprint: | QE 2021-10-04, QE 2021-10-18, QE 2021-11-01, QE 2021-11-15, QE 2021-11-29 | ||||
| Participants: | |||||
| Linked BF Score: | 141 | ||||
| Description |
|
NOTE There is ongoing work to create a new plan cache just for SBE plans. That work may affect what we decide to do here. The assignee of this ticket should ensure that the plan for the SBE plan caching project does not conflict with what we do under this ticket. The plan cache will only store winning solutions for the "lower" part of a QSN tree (the result of multi planning). To build an execution tree from a cache entry, we will first have to graft the 'postMultiPlan' QSN tree onto the QSN tree of the winning plan. This work will also involve modifying replanning code to only perform re-planning on portions of the tree that are multi-planned. There may also be some work to change the re-planning code to only use the number of reads done by the 'left' side of the query. |
| Comments |
| Comment by Githook User [ 18/Nov/21 ] |
|
Author: {'name': 'Irina Yatsenko', 'email': 'irina.yatsenko@mongodb.com', 'username': 'IrinaYatsenko'}Message: |
| Comment by Githook User [ 04/Nov/21 ] |
|
Author: {'name': 'Irina Yatsenko', 'email': 'irina.yatsenko@mongodb.com', 'username': 'IrinaYatsenko'}Message: |
| Comment by Githook User [ 02/Nov/21 ] |
|
Author: {'name': 'Irina Yatsenko', 'email': 'irina.yatsenko@mongodb.com', 'username': 'IrinaYatsenko'}Message: |