[
https://issues.apache.org/jira/browse/CASSANDRA-20191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17949849#comment-17949849
]
Caleb Rackliffe commented on CASSANDRA-20191:
---------------------------------------------
One thing we want to figure out (with our second committer reviewer) is whether
this actually needs to hit 5.0.x. It is an improvement, and not a bug fix, but
it might be easier to just port than wait until someone comes to us with a
profile that points to reading postings that we should have skipped :D
> Optimize initial skipping logic for SAI queries on large partitions
> -------------------------------------------------------------------
>
> Key: CASSANDRA-20191
> URL: https://issues.apache.org/jira/browse/CASSANDRA-20191
> Project: Apache Cassandra
> Issue Type: Improvement
> Components: Feature/SAI
> Reporter: Caleb Rackliffe
> Assignee: Sunil Ramchandra Pawar
> Priority: Normal
> Fix For: 5.0.x, 5.x
>
> Attachments: test-histogram_with_changes.html,
> test-histogram_without.html
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> In {{StorageAttachedIndexSearcher.ResultRetriever}}, we skip all postings
> lists produced by queries on individual column indexes to the first partition
> in the provided {{DataRanges}}. This is an obvious and useful step, but for
> queries on large partitions, it might not go as far as it could. If paging or
> user restrictions on the clustering key space are in play, it is probably
> suboptimal to not even attempt to skip the postings, which are
> row-addressable, to the first row after the clustering prefix in the (likely
> single) {{DataRange}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
