[SERVER-72233] [CQF] Do not explain Bindblock for IndexScan, PhysicalScan, ValueScan Created: 17/Dec/22 Updated: 29/Oct/23 Resolved: 20/Jan/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.3.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Svilen Mihaylov (Inactive) | Assignee: | Will Buerger |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | cascades-starter, explain | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Query Optimization
|
| Backwards Compatibility: | Fully Compatible |
| Sprint: | QO 2023-01-23 |
| Participants: |
| Description |
|
Do not explain the bindblock for V1-V2 type explains. The bind block is redundant. The bound projections can be inferred from the field projection map. |
| Comments |
| Comment by Githook User [ 20/Jan/23 ] |
|
Author: {'name': 'Will Buerger', 'email': 'will.buerger@mongodb.com', 'username': 'wbuerger46'}Message: |
| Comment by David Percy [ 20/Dec/22 ] |
|
Should we omit this from the output of SargableNode too? Should we also omit the RefBlock? |