Improve GpuExpand by pre-projecting some columns #25
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Firestarman <[email protected]>
Signed-off-by: Firestarman <[email protected]>
Signed-off-by: Firestarman <[email protected]>
firestarman
force-pushed
the
expand-improve
branch
from
48fadce
to
75728b3
Compare
firestarman
added a commit
that referenced
this pull request
Jan 22, 2024
Some rules in Spark will put non-leaf expressions into Expand projections, then it can not leverage the GPU tiered projection across the projection lists. So this PR tries to factor out these expressions and evaluate them before expanding to avoid duplicate evaluation for semantic-equal (sub) expressions. --------- Signed-off-by: Firestarman <[email protected]>
firestarman
added a commit
that referenced
this pull request
Jan 25, 2024
Some rules in Spark will put non-leaf expressions into Expand projections, then it can not leverage the GPU tiered projection across the projection lists. So this PR tries to factor out these expressions and evaluate them before expanding to avoid duplicate evaluation for semantic-equal (sub) expressions. --------- Signed-off-by: Firestarman <[email protected]>
firestarman
added a commit
that referenced
this pull request
Jan 25, 2024
Some rules in Spark will put non-leaf expressions into Expand projections, then it can not leverage the GPU tiered projection across the projection lists. So this PR tries to factor out these expressions and evaluate them before expanding to avoid duplicate evaluation for semantic-equal (sub) expressions. --------- Signed-off-by: Firestarman <[email protected]>
firestarman
added a commit
that referenced
this pull request
Jan 25, 2024
Some rules in Spark will put non-leaf expressions into Expand projections, then it can not leverage the GPU tiered projection across the projection lists. So this PR tries to factor out these expressions and evaluate them before expanding to avoid duplicate evaluation for semantic-equal (sub) expressions. --------- Signed-off-by: Firestarman <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Some rules in Spark will put non-leaf expressions into Expand projections,
then it can not leverage the GPU tiered projection across the projection lists.
So this PR tries to factor out these expressions and evaluate them before
expanding to avoid duplicate evaluation for semantic-equal (sub) expressions.