Uh oh!
There was an error while loading. Please reload this page.
Use the upstream arrow-rs coalesce kernel - #17193
Conversation
8dec409 to
d303a4dComparezhuqi-lucas
commented
Oct 28, 2025
Hi @alamb I am reviving this PR since the upstream arrow-rs has be upgraded, thanks! |
alamb
commented
Oct 28, 2025
Thank you @zhuqi-lucas -- I was just thinking the other day that we (I really) have dropped the ball on the coalesce kernel. I feel like once we get it into DataFusion we can then drive improvements upstream in arrow... |
alamb
commented
Oct 28, 2025
🤖 |
alamb
commented
Oct 28, 2025
🤖: Benchmark completed Details |
alamb
commented
Oct 28, 2025
🤖 |
alamb
commented
Oct 28, 2025
🤖: Benchmark completed Details |
alamb
commented
Oct 28, 2025
🤖 |
alamb
commented
Oct 28, 2025
🤖: Benchmark completed Details |
zhuqi-lucas
commented
Oct 29, 2025
Thank you @alamb for benchmark, the result is good! |
alamb
commented
Oct 29, 2025
I agree the benchmarks look good to me (no significant difference in performance) @zhuqi-lucas would it be ok to update the title of this PR and its description? I think the core change here is to use the upstream 'coalesce' kernel. Is that your understanding too? |
zhuqi-lucas
commented
Oct 29, 2025
Updated the title now, thank you @alamb . |
Uh oh!
There was an error while loading. Please reload this page.
zhuqi-lucas
commented
Oct 31, 2025
Thank you @alamb@2010YOUY01 for review! Merged now. |
alamb
commented
Oct 31, 2025
Awesome -- one step closer |
## Which issue does this PR close? Use the upstream arrow-rs coalesce kernel, and support LimitedBatchCoalesce for datafusion ## Rationale for this change Use the upstream arrow-rs coalesce kernel, also it will support LimitedBatchCoalesce for datafusion. There are some future work based this, for example [Push limit into joins ](apache#18295) which will optimize join. ## What changes are included in this PR? <!-- There is no need to duplicate the description in the issue here but it is sometimes worth providing a summary of the individual changes in this PR. --> ## Are these changes tested? <!-- We typically require tests for all PRs in order to: 1. Prevent the code from being accidentally broken by subsequent changes 2. Serve as another way to document the expected behavior of the code If tests are not included in your PR, please explain why (for example, are they covered by existing tests)? --> ## Are there any user-facing changes? <!-- If there are user-facing changes then we may require documentation to be updated before approving the PR. --> <!-- If there are any breaking changes to public APIs, please add the `api change` label. --> --------- Co-authored-by: Andrew Lamb <andrew@nerdnetworks.org> Co-authored-by: Daniël Heres <danielheres@gmail.com>
## Which issue does this PR close? Use the upstream arrow-rs coalesce kernel, and support LimitedBatchCoalesce for datafusion ## Rationale for this change Use the upstream arrow-rs coalesce kernel, also it will support LimitedBatchCoalesce for datafusion. There are some future work based this, for example [Push limit into joins ](apache#18295) which will optimize join. ## What changes are included in this PR? <!-- There is no need to duplicate the description in the issue here but it is sometimes worth providing a summary of the individual changes in this PR. --> ## Are these changes tested? <!-- We typically require tests for all PRs in order to: 1. Prevent the code from being accidentally broken by subsequent changes 2. Serve as another way to document the expected behavior of the code If tests are not included in your PR, please explain why (for example, are they covered by existing tests)? --> ## Are there any user-facing changes? <!-- If there are user-facing changes then we may require documentation to be updated before approving the PR. --> <!-- If there are any breaking changes to public APIs, please add the `api change` label. --> --------- Co-authored-by: Andrew Lamb <andrew@nerdnetworks.org> Co-authored-by: Daniël Heres <danielheres@gmail.com>
Which issue does this PR close?
Use the upstream arrow-rs coalesce kernel, and support LimitedBatchCoalesce for datafusion
Rationale for this change
Use the upstream arrow-rs coalesce kernel, also it will support LimitedBatchCoalesce for datafusion. There are some future work based this, for example Push limit into joins which will optimize join.
What changes are included in this PR?
Are these changes tested?
Are there any user-facing changes?