CASSANDRA-20154: Fix BETWEEN bounds to preserve inverted bounds #4412
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.
Fix CASSANDRA-20154: BETWEEN operator returns wrong results when start bound is greater than end bound.
This PR fixes a bug where queries like
SELECT * FROM table WHERE column BETWEEN 5 AND 3
incorrectly return rows instead of an empty result set. The issue was caused by Cassandra
automatically sorting BETWEEN bounds, which violates SQL standards.
Changes made:
Before:
WHERE pk BETWEEN 5 AND 3
would return rows between 3 and 5After:
WHERE pk BETWEEN 5 AND 3
correctly returns no rows (as per SQL standard)By Arvind Kandpal for CASSANDRA-20154