[SERVER-68934] Audit treatment of Nothing in lowering code Created: 18/Aug/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: | Task | Priority: | Major - P3 |
| Reporter: | Hana Pearlman | Assignee: | Davis Haupt (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 |
| Sprint: | QO 2023-01-23 |
| Participants: |
| Description |
|
This ticket is to audit treatment of Nothing in the lowering code to understand where & why we need fillEmpty and to see if handling of Nothing is missing anywhere. For example, when lowering PathComposeA/M in the Filter context, we use fillEmpty on the first child path, which is the input to an If expression. Is this necessary? Should we have a fillEmpty on the second path as well? |
| Comments |
| Comment by Githook User [ 20/Jan/23 ] |
|
Author: {'name': 'Davis Haupt', 'email': 'davis.haupt@mongodb.com', 'username': 'davish'}Message: |