New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ARROW-10685: [Rust] [DataFusion] Added support for Join on filter-pushdown optimizer. #8738
Conversation
fyi @andygrove and @alamb :) |
left_cols, | ||
right_cols, | ||
)? | ||
.join(&right.to_logical_plan(), join_type, left_cols, right_cols)? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is unrelated: it is just a small simplification to the signature of LogicalPlanBuilder::join
to not require the Arc
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I haven't done a thorough review but I pulled these changes and test them against TPC-H query 12 and it worked great.
@jorgecarleitao could you try pushing an empty commit to trigger CI again? |
…hdown optimizer. This PR extends the filter pushdown optimizer to support nodes of multiple children. In the context of the `join`, this allows to push filters down the joins. E.g. ``` "\ Filter: #a LtEq Int64(1)\ \n Join: a = a\ \n TableScan: test projection=None\ \n TableScan: test projection=None" ``` is optimized to ``` "\ Join: a = a\ \n Filter: #a LtEq Int64(1)\ \n TableScan: test projection=None\ \n Filter: #a LtEq Int64(1)\ \n TableScan: test projection=None" ``` This also reduces the complexity of the optimizer by making it perform a single pass on the plan. Naturally, this has a major implication in performance as the `join` is an expensive operation. Closes apache#8738 from jorgecarleitao/filter_push Authored-by: Jorge C. Leitao <jorgecarleitao@gmail.com> Signed-off-by: Andy Grove <andygrove73@gmail.com>
This PR extends the filter pushdown optimizer to support nodes of multiple children. In the context of the
join
, this allows to push filters down the joins. E.g.is optimized to
This also reduces the complexity of the optimizer by making it perform a single pass on the plan.
Naturally, this has a major implication in performance as the
join
is an expensive operation.