[
https://issues.apache.org/jira/browse/CASSANDRA-21635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Caleb Rackliffe updated CASSANDRA-21635:
----------------------------------------
Fix Version/s: 5.0.10
6.0-alpha3
(was: 5.0.x)
(was: 6.0.x)
Since Version: 5.0.0
Source Control Link:
https://github.com/apache/cassandra/commit/7ee239aac969dcc7bac72fff4e4662fae88ded76
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
> IndexTermType#comparator() Handles Reversed Types Incorrectly
> -------------------------------------------------------------
>
> Key: CASSANDRA-21635
> URL: https://issues.apache.org/jira/browse/CASSANDRA-21635
> Project: Apache Cassandra
> Issue Type: Bug
> Components: Feature/SAI
> Reporter: Caleb Rackliffe
> Assignee: Caleb Rackliffe
> Priority: Normal
> Fix For: 5.0.10, 6.0-alpha3, 7.x
>
> Attachments: ci_summary-2.html, ci_summary-3.html, ci_summary.html,
> result_details.tar-1.gz, result_details.tar-2.gz, result_details.tar.gz
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> {{IndexTermType#comparator()}} has only one caller in {{V1SSTableIndex}}.
> It's used there to establish the min and max terms across segments.
> Unfortunately, {{comparator()}} does not unwrap reversed clustering keys like
> {{compare()}} does, and with incorrect min/max, queries will miss data.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
