[
https://issues.apache.org/jira/browse/CASSANDRA-20334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17934357#comment-17934357
]
Caleb Rackliffe edited comment on CASSANDRA-20334 at 3/12/25 1:57 AM:
----------------------------------------------------------------------
|[trunk|https://github.com/apache/cassandra/pull/3970]| [^ci_summary.html] |
was (Author: maedhroz):
|[trunk|https://github.com/apache/cassandra/pull/3970]|CI TODO|
> Deprioritize SAI index by default when multiple index types exist on a column
> -----------------------------------------------------------------------------
>
> Key: CASSANDRA-20334
> URL: https://issues.apache.org/jira/browse/CASSANDRA-20334
> Project: Apache Cassandra
> Issue Type: Bug
> Components: Feature/2i Index, Feature/SAI
> Reporter: Caleb Rackliffe
> Assignee: Caleb Rackliffe
> Priority: Normal
> Fix For: 5.0.x, 5.x
>
> Attachments: ci_summary.html, result_details.tar.gz
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> SASI and later SAI, in lieu of anything resembling a query planner, have
> always just greedily returned a min long from
> {{Index#getEstimatedResultRows()}}, thereby stealing the right to be used to
> execute the query even when a legacy 2i is present on the relevant columns.
> If we have a user that needs to migrate away from a legacy 2i, this seems
> like the exact opposite of what we want to do by default. I want to propose
> that we invert this behavior, and have legacy 2i continue to serve queries
> instead of new SAI indexes by default until they are dropped.
> Note that we'll have more options around this when CASSANDRA-18112 lands, but
> for now the change in default seems valuable.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
