[SERVER-79034] [CQF] Satisfy RemoveOrphansRequirement in ScanNode implementer Created: 17/Jul/23 Updated: 29/Oct/23 Resolved: 04/Aug/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.1.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Ben Shteinfeld | Assignee: | Richard Hausman (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Query Optimization
|
| Backwards Compatibility: | Fully Compatible |
| Participants: |
| Description |
|
In many cases, plans will have a SargableNode which will satisfy RemoveOrphansRequirement ( We could rely the existing enforcer for RemoveOrphansRequirement to generate a physical alternative, but this won't take advantage of the ability to push down top-level field projections into the physical scan. We should take care to test dotted field paths. |
| Comments |
| Comment by Githook User [ 07/Aug/23 ] |
|
Author: {'name': 'Richard Hausman', 'email': 'richard.hausman@mongodb.com', 'username': 'rhausman'}Message: |
| Comment by Githook User [ 04/Aug/23 ] |
|
Author: {'name': 'Richard Hausman', 'email': 'richard.hausman@mongodb.com', 'username': 'rhausman'}Message: |