You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "ZhaoYang (Jira)" <ji...@apache.org> on 2020/08/11 07:51:00 UTC
[jira] [Updated] (CASSANDRA-16044) Query SSTable Indexes lazily in
token sorted runs for LCS, TWCS or RangeAwaredCompaction
[ https://issues.apache.org/jira/browse/CASSANDRA-16044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ZhaoYang updated CASSANDRA-16044:
---------------------------------
Summary: Query SSTable Indexes lazily in token sorted runs for LCS, TWCS or RangeAwaredCompaction (was: Query SSTable Indexes in token sorted runs for LCS and TWCS)
> Query SSTable Indexes lazily in token sorted runs for LCS, TWCS or RangeAwaredCompaction
> ----------------------------------------------------------------------------------------
>
> Key: CASSANDRA-16044
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16044
> Project: Cassandra
> Issue Type: Improvement
> Components: Feature/SASI
> Reporter: ZhaoYang
> Priority: Normal
>
> Currently SASI searches all SSTable indexes that may include the query partition key and indexed term, but this will cause large IO overhead with range index query (ie. age > 18) when sstable count is huge.
> Proposed improvement: query sstable indexes in token-sorted-runs lazily. When the data in the first few token ranges is sufficient for limit, SASI can reduce the overhead of searching sstable indexes for the remaining ranges.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org