ARROW-10701: [Rust] Fix sort_limit_query_sql benchmark #8745
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
I probably introduced this bug some time ago, but there was another bug in the benchmark setup that caused the query to not be executed, only planned.
alamb
approved these changes
Nov 25, 2020
|
This time @nevi-me beat me to the merge 🏃 👍 |
GeorgeAp
pushed a commit
to sirensolutions/arrow
that referenced
this pull request
Jun 7, 2021
I probably introduced this bug some time ago, but there was another bug in the benchmark setup that caused the query to not be executed, only planned. Closes apache#8745 from jhorstmann/ARROW-10701-fix-sort-limit-query-benchmark Authored-by: Jörn Horstmann <joern.horstmann@signavio.com> Signed-off-by: Neville Dipale <nevilledips@gmail.com>
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.
I probably introduced this bug some time ago, but there was another bug in the benchmark setup that caused the query to not be executed, only planned.