[SERVER-82238] Add field to explain to indicate if winning and rejected plans are cached Created: 16/Oct/23 Updated: 03/Jan/24 Resolved: 28/Dec/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.3.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Matt Boros | Assignee: | Matt Boros |
| 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: | QO 2023-11-27, QO 2023-12-11 | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Description |
|
To aid in support cases and allow explain to convey information about the cached plan (since usually it is ignored), we should add an "isCached" field to all plans listed in explain. This will be a boolean to indicate whether the plan matches the cached plan. For support cases where a bad plan is cached and the user runs explain and sees a different plan reported, the issue will be more obvious. We can also add a top level field "doesWinningPlanMatchCached" to surface this even higher. |
| Comments |
| Comment by Githook User [ 28/Dec/23 ] |
|
Author: {'name': 'Matthew Boros', 'email': 'mattBoros@users.noreply.github.com', 'username': 'mattBoros'}Message: GitOrigin-RevId: 1ce84ae1bac7fc36edcabc29bad9abf6c3027bf2 |
| Comment by Matt Boros [ 07/Dec/23 ] |
|
|