[SERVER-68377] Avoid reading the special dense column if reading a known to be dense path Created: 27/Jul/22 Updated: 29/Oct/23 Resolved: 21/Dec/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.3.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Irina Yatsenko (Inactive) | Assignee: | Dianna Hohensee (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | pm2646-m5 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | QE 2022-11-14, QE 2022-11-28, QE 2022-12-12, QE 2022-12-26 |
| Participants: |
| Description |
|
Currently, the column_scan stage always reads the special dense column in absence of filters. There are two issues to consider:
|
| Comments |
| Comment by Githook User [ 21/Dec/22 ] |
|
Author: {'name': 'Dianna Hohensee', 'email': 'dianna.hohensee@mongodb.com', 'username': 'DiannaHohensee'}Message: |