[
https://issues.apache.org/jira/browse/CASSANDRA-19968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Caleb Rackliffe updated CASSANDRA-19968:
----------------------------------------
Attachment: ci_summary-1.html
> Partition-restricted index and queries that use strict replica filtering can
> use SinglePartitionReadCommand
> -----------------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-19968
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19968
> Project: Cassandra
> Issue Type: Improvement
> Components: Consistency/Coordination, Feature/2i Index, Feature/SAI
> Reporter: Caleb Rackliffe
> Assignee: Caleb Rackliffe
> Priority: Normal
> Fix For: 5.0.x, 5.x
>
> Attachments: ci_summary-1.html, ci_summary.html
>
>
> Index and filtering queries have historically always been treated as range
> reads. However, when they are restricted to a partition, there is no reason
> they cannot be handled like single-partition reads, flowing through
> {{StorageProxy#fetchRows()}}. The benefit of doing this is that we may be
> able to take advantage of digest reads. The caveat is that this may not be
> possible (or worthwhile) when, for instance, SAI queries do not use strict
> filtering. When strict filtering is not active, we may need to filter
> combined replica results at the coordinator even when there isn’t a digest
> mismatch. When there is a digest mismatch, replica filtering protection will
> kick in during the read repair process and safely resolve this.
> tl;dr We can safely treat partition-restricted index/SAI/filtering queries as
> single-partition reads, but initially it may be safest to do this only when
> strict filtering is enabled.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
