Add utf8view benchmark for aggregate topk #15518
Merged
Conversation
This file contains hidden or 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
github-actions
bot
added
core
zhuqi-lucas
force-pushed
the
utf8view_benchmark_aggregation_topk
branch
from
3392cec to
4387774
Compare
nirnayroy
pushed a commit
to nirnayroy/datafusion
that referenced
this pull request
May 2, 2025
* Fix * fix fmt
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Which issue does this PR close?
Since we have merged the utf8view support for aggregate topk, so also add the corresponding benchmark code in this PR.
#15152
Close part of #15096
Rationale for this change
Since we have merged the utf8view support for aggregate topk, so also add the corresponding benchmark code in this PR.
What changes are included in this PR?
Since we have merged the utf8view support for aggregate topk, so also add the corresponding benchmark code in this PR.
Are these changes tested?
Yes
Are there any user-facing changes?
No