[SERVER-67335] Ensure COLUMN_SCAN appears in slow query log lines for plans using it Created: 16/Jun/22 Updated: 29/Oct/23 Resolved: 30/Jun/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying |
| Affects Version/s: | None |
| Fix Version/s: | 6.1.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Charlie Swanson | Assignee: | Jeffrey Xiao |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
This may just work, but we should add some tests to demonstrate it and also make sure it is clear which columns are being scanned. We should probably also think about whether we want the slow query log line to include other more detailed stats like whether/how often it needed to fall back to the row store. |
| Comments |
| Comment by Githook User [ 30/Jun/22 ] |
|
Author: {'name': 'Jeffrey Xiao', 'email': 'jeffrey.xiao@mongodb.com', 'username': 'jxiao'}Message: |