Skip to content

feat: Avoid duplicate PhyscialExpr evaluation on hash table #16719

Closed
jonathanc-n wants to merge 4 commits intoapache:mainfrom
jonathanc-n:optimize-hashing
Closed

feat: Avoid duplicate PhyscialExpr evaluation on hash table #16719
jonathanc-n wants to merge 4 commits intoapache:mainfrom
jonathanc-n:optimize-hashing

Conversation

@jonathanc-n
Copy link
Contributor

Which issue does this PR close?

  • Closes #.

Rationale for this change

While looking into hash join spilling I noticed that the physical expression is being executed twice when creating JoinLeftData; once when updating hash and once to return the left side data.

What changes are included in this PR?

Remove the duplication. Evaluate indices once and hand it to update_hash then concatenate together to form JoinLeftData.

Are these changes tested?

By existing tests

@github-actions github-actions bot added datasource Changes to the datasource crate physical-plan Changes to the physical-plan crate labels Jul 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

datasource Changes to the datasource crate physical-plan Changes to the physical-plan crate

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant