[SERVER-68519] Better explain for column scan Created: 02/Aug/22 Updated: 29/Oct/23 Resolved: 14/Oct/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.2.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Irina Yatsenko (Inactive) | Assignee: | Alyssa Clark |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | QE 2022-10-17 |
| Participants: |
| Description |
|
Column scan can get complicated with filters push down, optimized projections, etc. We should review explain output for plans with a column scan and augment both SBE part and possibly the QSN part with relevant, human-readable info. Also change stage name from "COLUMN_SCAN" to lower case w/o underscores. |
| Comments |
| Comment by Githook User [ 14/Oct/22 ] |
|
Author: {'name': 'Alyssa Wagenmaker', 'email': 'alyssa.wagenmaker@mongodb.com', 'username': 'awagenmaker'}Message: |