Make cassandra.partition-size-for-batch-select work expectedly #21940
+105
−1
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.
Description
This PR fixes
cassandra.partition-size-for-batch-select
behavior that uses one more partition than expected when executing CQLs.Additional context and related issues
Steps to reproduce
Firstly, prepare a Cassandra table and records:
Then, launch trino-esrver-dev with the following changes:
After the server launches, you can reproduce the bug by executing the following Trino query:
Here is an output from the server, and, as you can see in the log, the CQL Trino executed includes three partitions even though we set
cassandra.partition-size-for-batch-select
to 2.The expected output should be as follows (I got the log when I checked the behavior of this PR):
Release notes
( ) This is not user-visible or is docs only, and no release notes are required.
( ) Release notes are required. Please propose a release note for me.
(x) Release notes are required, with the following suggested text: