Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Support split non-AST-able join condition for BroadcastNestedLoopJoin #9635
Support split non-AST-able join condition for BroadcastNestedLoopJoin #9635
Changes from all commits
3f50f88
2638ce8
a40f9a5
3e19600
542e1ae
f3ad734
8be33c1
d2d6277
d63bca6
6546c3c
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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 think this should be fine, but I am not 100% sure that
convertToGpu
will be idempotent. It might be better to just convert it to the GPU up front and cache it instead of recalling it inside ofsplitNonAstInternal
. To make that work we probably would have to zip the GPU expression and along withcondition.childExprs
. I don't think this is a blocker for the patch to go in. Just being overly cautious about it.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.
Hmm, it seems not very straight forward to eliminate non-idempotent risk here.
convertToGpu
only happens when we need to replace it with a new GpuAlias node. We can probably cache those converted expression but in the end (L100), the rootBaseExprMeta
will do a realconvertToGpu
which converts the entire tree. It seems we can hardly reuse the cache here.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 think this is fine for now, so lets file a follow on issue to look into it. I see a few ways to fix it, but none of them are that simple, and may have their own hidden pitfalls.