Implement projection pushdown for EXISTS subqueries #238
Conversation
This change introduces an optimization to push projections down into `EXISTS` subqueries. Previously, the projection optimizer did not traverse into `EXISTS` subquery plans, preventing it from pruning unused columns within the subquery. This commit addresses this by recursively calling the `optimize_projections` rule on the subquery's plan, with the knowledge that no columns are required from its output. This allows the optimizer to eliminate unnecessary columns and reduce the amount of data processed by the subquery.
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
This change introduces an optimization to push projections down into
EXISTSsubqueries, allowing the optimizer to prune unused columns and reduce the amount of data processed by the subquery.PR created automatically by Jules for task 14687139752140503176 started by @Dandandan